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

[Nic Brough -Adaptavist- · Accepted solution]

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.

[Jose Ramirez]

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]

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.

[Nic Brough -Adaptavist-]

In this case, your team is "the housebuilders", of which you might assign different subtasks individually to people with specialisations.

It does not make sense to have a team on a sub-task, the team should be that of the parent.

[Lee Heath]

@Nic Brough -Adaptavist- you seem very dismissive and rude - are you sure this is correct responsibility for you?

Community Leader

Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.

[Nic Brough -Adaptavist-]

@Lee Heath - yes, I know, I write poorly sometimes, and come across as grumpy.  I do not mean to be.

This happens more when people are not reading (or maybe not understanding) what I wrote.

[Max Santos]

Imagine we have a project that includes things created by two internal teams and two external teams.

Do i need to create a Specific Team that includes all these people in order to attribute tasks to them?

Is so, i would almost need to create a "fake" team (the the housebuilders) every-time a story needs different set of teams.

A second scenario is for example the report of a bug on a software, an issue is created an attributed to a team, that team investigates and realizes that it needs the intervention of a second team. 
How is this supposed to work if then can't create a task for that team?
This is a honest question, i really would like to know what is the standard way of solving this.

I actually agree, it would be extremely useful to have a task be attributed to a team other than the owner.

[Nic Brough -Adaptavist-]

You assign stories or tasks to the teams as appropriate.  Not fragments of a story.