Teams in Advanced Roadmaps
The teams field is a custom field in Jira Software. To make this field appear in Jira Software issues, you'll first need to add this custom field to the screen that's being used in the corresponding Jira Software project.
Once configured, Teams in Advanced Roadmaps act as a label to designate which team will eventually pick up the work on your timeline. Once saved, you can search for issues that have been labeled for that team, then assign them to individuals when grooming your backlog.
There are two types of teams to choose from in Advanced Roadmaps:
- Private teams only exist within your plan so you can explore what-if scenarios and see how changes to your teams will affect your plan. This is what Advanced Roadmaps refers to as Scenario planning.
- Shared teams are visible across your organization and can be assigned to work on multiple plans.
In the Teams tab underneath your plan name, you’ll see the list of teams included in your plan, as in the example below:
This team snapshot includes:
- the issue source associated to the team
- the capacity and iteration length (capacity information will vary depending on whether it’s a Scrum or Kanban team, as well as how their work is estimated)
- members of the team
- whether the team is shared or private (indicated by the lozenge)
You can also Filter issues by this team to view only the issues assigned to the specific team in your plan.
You need Advanced Roadmaps user permission to save team changes in Jira Software.
Create a new team
Every team you create in Advanced Roadmaps will begin as a private team and will only exist within this specific plan. Once created, you can convert a private team to a shared team. This cannot be reversed.
To create a new private team:
- In the Teams tab, navigate to + Add team > New private team.
- Choose a name for your team, then select an issue source that you want to associate with the team. Issues from this issue source will be given a higher priority for this team. Learn more about Issue sources.
- Choose whether your new team will be a Scrum team or a Kanban team, then set the iteration length and capacity. The type of team you choose will have an impact on how capacity is handled and managed in a plan.
- Add members to the team.
- When you’re happy with your team, select Create.
Your team will now be available in your plan, but the changes won’t be finalized until you Save selected changes in Jira using the Review changes button.
Convert a plan-only team to a shared team
This process can't be reversed.
To convert a plan-only team to a shared team:
- Navigate to the Teams tab
- On the team you’d like to convert, open the menu, then choose Share
- If the Share button doesn’t show (and your team has a yellow bar on its side), you’ll need to save the team first using the Review changes button. Learn more about reviewing and saving changes in Advanced Roadmaps
- Select Share in the modal that pops up.
Once shared, you can then assign it to issues across multiple plans.
Add a shared team
To add a shared team to a plan:
- In the Teams tab, navigate to + Create team > Add existing shared team.
- Start typing to find the team you’d like to add. Select the team > Add shared team.
Edit a team
Whether it's a private team or a shared team, you can edit the following details:
- team name
- associated issue source
- capacity and iteration length
- team type (only if all teams in the plan use time-based estimates)
To edit a team, navigate to the Teams tab and select more > Edit for the team you want to edit. Modify the details of the team, then select Save.
Assign work to a team
Once your teams are set up, you can easily assign any issues by typing the team’s name into the Team column of your plan.
Delete a team
When a team is no longer needed, you can remove them from your plan. Shared teams can be re-added to your plan, but you can’t recover a deleted private team.
To delete a team
- Navigate to the Teams tab
- Select more > Delete, and Advanced Roadmaps will remove the team from your plan.
Was this helpful?Yes Provide feedback about this article