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.
A guide on how to deploy and monitor an application built on AWS using Atlassian and third-party tools.
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.
By default, single-project releases that are contained within a cross-project release can have their own dates. However, if you want all of your single-project releases to converge or begin at the same time,Advanced Roadmaps lets you align releases using either the start or end dates.
A cross-project release is a way to align multiple single-project releases, and is only used for planning purposes in Advanced Roadmaps. They can’t be saved back to your Jira issues. When you save a cross-project release, only the single-project release associated with the teams in your plan will be updated.
To align the dates of single-project releases in a cross-project release:
Navigate to the Releases view from the plan view dropdown, and find the cross-project release whose release dates you want to align.
Select more () > Align dates.
Choose how you want to align the start and/or end dates.
When you’re done, select Set dates to update the dates in your plan.
Release start date options:
As early as possible - The release will start as soon as there are available teams to work on the issues in the release. This is mostly only used when auto-scheudling issues.
Fixed date - Set a date
Relative to previous release date - Automatically trigger a new release a certain amount of time after the previous release finishes. For example, you can start work on the beta release one day after work for the alpha is completed.
Release date end options:
After all issues are completed - The release date is flexible and doesn’t display in the plan.
Fixed date - The release will happen on this chosen date, overriding the capacity and velocity settings. The release icons on the timeline will turn red for overbooked releases.
Was this helpful?