Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,300
Community Members
 
Community Events
176
Community Groups

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

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

1 answer

1 accepted

1 vote
Answer accepted

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.

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

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.

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.

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.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events