nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Subtask: why can't I choose a team in team field?

Evgeniya Vigil

Hi,

I've added a new field "Team" for all issue types. I can choose a Team (for example "WEB") in Epic and in Task, but in the field in Sub-Tasks is this field not klickable. Therefore I can't choose anything in this field. How can I resolve the problem? Can anybody pls help me?

Thank you in advance!

Regards,

Evgeniya

Accepted answers

Nic Brough -Adaptavist-

Welcome to the Atlassian Community!

It doesn't make sense to apply a team field to sub-tasks. In Jira, sub-tasks are very much a part of their parent story, not separate items. If a task or story has a team, then the sub-tasks must belong to that team as well, because they own the whole story.

It's a bit of a pain for reporting as you can't find sub-tasks for a team (it should cascade down really), but it is the right behaviour.

All comments

Nic Brough -Adaptavist-

Welcome to the Atlassian Community!

It's a bit of a pain for reporting as you can't find sub-tasks for a team (it should cascade down really), but it is the right behaviour.

JMR

I strongly disagree. A sub-task can be assigned to a different team, even an external team. This limitation is not reasonable.

Nic Brough -Adaptavist-

Nope, rubbish. If you give a Jigsaw to someone, how are they going to complete it if you give some of the pieces of it to someone else in a different house?

If you have stories that need doing by different teams, then, by definition, they can't be pieces of the same story.

Orlando Kelly_roz6cy

we have tasks broken down into subtasks that we would like to assign to different teams, The story may be to complete "building a room in a house" one of the subtasks may involve a team specializing in installing the electrical components, (in our case, the networking involving our external palo alto firewalls) In this case the dev team has no access to that, but rely on the corporate networking team.

So we have several subtasks that make up the whole story that needs to be completed.

Now we could create a completely separate tasks and have a relationship to the main task, but we like the structure of subtasks to make sure all the work is completed.

I don't think there is any right way to do this, just the stage we have go to in our agile journey.

So allowing teams to use subtasks and assign teams should be a valid option for people looking to use that functionality.