What is the purpose of Team Members of Advanced Roadmap Teams

[Manouil Gioulountas]

I am setting up an advanced roadmap plan and have created teams, but I cannot find any information or evidence of the purpose of setting up the team members. I was expecting setting teams members would be used to auto-assign tickets to a Team, but that does not seem to be the case.

[Mark Segall · Accepted solution]

Hi @Manouil Gioulountas - There are two primary purposes for teams:

1. When you have multiple teams sharing the same project, teams will provide a mechanism for being able to filter their work on the plan
2. You can use them to get some light capacity management capability (You can find more on this functionality HERE)

[Manouil Gioulountas]

I didn't ask about teams. I asked about members.

[Mark Segall]

Sorry - I misread the question.  They primarily play into the auto-scheduler capability.  It doesn't necessarily care about individual team members as much as how many individuals make up the team to calculate how many issues can be taken on in parallel for a given sprint. Here's more info on it:

https://support.atlassian.com/jira-software-cloud/docs/how-does-the-auto-scheduler-in-advanced-roadmaps-work/

[Manouil Gioulountas]

I see. This was my assumption but was hoping I was wrong. A shame, but thank you for the info.

[Mark Segall]

If you're looking for automated team assignments, there are a couple possibilities:

1. Use Automation:  The Assign Issue action provides a mechanism for assigning based upon "Balanced Workload", "Random", or "Round Robin".  You can use roles, groups, or manually set.  I would recommend triggering on Field Value Changed (Sprint)
2. Use Components: This is the simplest in terms of configuration but you could assign component leads.  For example, user 1 always gets issues tagged with a component of "Developer", user 2, "QA", etc.

[Manouil Gioulountas]

Interesting, but that sounds more oriented toward assigning tickets to people rather than assigning tickets to teams. Though I assume the automation option would conversely allow setting a team. 

Either way, I have zero experience with Jira automation. I don't even know if it is available to me, will have to read up on it.

[Mark Segall]

Automation isn't too bad.  It can get very complex, but the basic principles are that there are 4 types of components that can make up a rule:

• Trigger (Green): How the rule knows when to fire (e.g. issue created, field value changed, etc.)
• Condition (Yellow): How you want the rule to filter through stuff (e.g. issue type = Story, status not equal closed, etc.)
• Action (Blue):  What you want the rule to accomplish (e.g. Edit Issue, Transition Issue, etc.)
• Branch (Purple): When you want to perform actions against a related issue (e.g. Issue's Epic or Sub-Task)

For this case, it does require a little bit more complexity, but it's possible:

First, you need the ID's of each Team that you wish to assign.  The easiest way to get this is by executing a search:

"Team[Team]" = YourTeamName

As you execute the search, Jira will convert the team name to its ID

Next is the automation rule. For my example below, I'm setting the team when the issue is created:

• TRIGGER: Issue Created
• ACTION: Edit Issue
  • More Options (copy/paste this and replace what's in bold with your team ID)

    • {"fields": {"customField_10001": "1"}}

Note - This rule will simply apply the same team to every issue that's created. If that meets your need, great.  Otherwise, you'll want to play with If/Else conditions.  I can help with that, I just need the business logic that will determine how the rule will know which team should be assigned the issue.

I hope this helps.