Learn how to set up Jira Software Cloud and integrate it with other products and applications.
Learn how to configure your Jira Software Cloud company-managed projects to suit your agile development processes.
Learn how to create, search, and work with issues in software projects, manage your profile, and more.
Learn how to get started, enable features, and manage and administer team-managed projects.
Plan and view work across multiple teams, projects, and releases with Advanced Roadmaps.
This page refers to Advanced Roadmaps, which is a cross-project planning tool only available as part of Jira Software Cloud Premium and Enterprise.
We have a separate section for documentation about the project roadmap that’s included in all Jira Software plans. Go to the documentation for project-level roadmaps in Jira Software.
The Team field is a custom field in Jira Software.
If you want to save this back to your Jira issues, you'll first need to add the Team field to the Jira screen. Learn more about this on the Enable custom fields used in Advanced Roadmaps in Jira page.
Teams in Advanced Roadmaps are different from the teams found in the rest of Jira Software Cloud. In Advanced Roadmaps, they act as a label applied to issues that designates which team will eventually pick up the work on your timeline. By adding the Team field to your Jira issues, you can save this value back to your Jira issues, which makes sprint planning easier.
Since Advanced Roadmaps is a planning tool, the Team field is a way to use features like capacity management without assigning issues to individuals, which happens in sprint grooming or planning sessions.
You can also use Advanced Roadmaps' view settings to focus on work assigned to a specific team. For example, you can choose to color issues based on the team to which they’re assigned, group issues by team on your timeline, or hide teams from your view.
Within Advanced Roadmaps, you have two options when making a team:
A shared team will be visible in all Advanced Roadmaps plans across your organization. Anyone can add this team to their plan, and begin to model future work based on its capacity, overall availability, and the members of the team.
A plan-only team lives only within your plan. If someone else in your organization makes a plan, they won’t be able to use this team. This is helpful if you’re planning for a team that doesn’t yet exist. You can always convert a plan-only team to a shared team at a later date.
Was this helpful?