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.
Create powerful rules to start automating your manual, repetitive processes.
Plan and view work across multiple teams, projects, and releases with Advanced Roadmaps.
A guide on how to deploy and monitor an application built on AWS using Atlassian and third-party tools.
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 Teams 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 Teams 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.
Releases in Advanced Roadmaps essentially function as large target deadlines for sections or versions of your work. In the rest of Jira, these are referred to as Fix versions.
You can set a release to happen on a set date, or after all of the issues assigned to it are completed. The former is recommended for teams that release with regular cadence (every two weeks) since any issues that aren’t completed can be bounced to the next release. For teams that have irregular releases, Advanced Roadmaps can give you a projected release date when you define a release based on completed issues.
Was this helpful?