Story Sub Tasks do not pick up the Story Team Name assignment

[Gordon Jones]

When creating sub tasks for a story within a Team, the sub-tasks do not seem to pick up the team name autmoatically.  We then have to manually assign the team name to the su-task.

Our reporting filters look to track and team productivity by team name and needs to see all issue the team is working.

Its a real pain to create a bunch of sub tasks for team members supporting the Story within that Sprint, then have to go back into each sub-task to assign the team name, so the sub-tasks show up in our productivity reports by assignee.

What am I missing?

[Bill Sheboy]

Hi @Gordon Jones 

What do you mean by "team"?  Unfortunately Jira has several things named "team".  For example, where do you create teams and manage their information in Jira.

Next, when setting the values of an issue's fields, it does not automagically assume the properties of its parent.  For example, some users may want different values in fields at different levels in the hierarchy.

For your use case, you might be able to copy those values from the parent to the child subtasks using an automation rule.  To learn if that is possible, let's first confirm if the "team" field is accessible to automation:

• find an example user story which has a Team set, and an example subtask of that user story which does not
• use this how-to article to find your Team field, and learn if it as a smart value in both the story and subtask, allowing access from the automation rule: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

If the field is accessible, you could create a rule to copy the value when a subtask is created.

Kind regards,
Bill

[Gordon Jones]

Thanks @Bill Sheboy 

That was very helpful.  I was able to locate the "Team" Smart Value field information.

{"self":"https://###############.atlassian.net/rest/api/2/customFieldOption/11320","value":"XX XXX XXXXXXXXXXX","id":"11320"}

I ran the tool on multiple tickets to prove the values across our internal teams.  As expected each team has a unique value.

To clarify, I would then use the following smart values in {{customerFieldOption=11320}}. within my automation.

Since there are multiple Team Board Names within our workspace, I am assuming I will need to create this automation assignment check for sub-tasks - one per team. 

What I'm still a bit unclear on.... is how to know the team name from the parent issue (Story or Task) to use in my assignment automation for sub-tasks.

[Bill Sheboy]

I am glad to learn you found your field.

When the automation rule's issue edit shows your field in the drop-downs, you can edit/update it that way.  When it is not shown, you need to use the advanced edit with JSON, such as:

{
  "fields": { 
    "customfield_11320": "the value I want to set"
  }
}

So if a parent issue has this data, it could be used to set the values in the subtasks.

You also noted "multiple Team Board Names".  Boards have nothing to do with Teams in Jira... a board is a view of a issues from one-or-more projects using a JQL filter.  Often when people have multiple boards in a project, there is something different about the issues which allows the JQL to separate them.  If the "team" field is how you do that, you might need different rules; it really depends about your project/board setup.