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.
A single-project release only contains one release from one project. Edits to it can be saved in Jira Software as a fix version.
A cross-project release lets you edit and track several single-project releases from multiple teams and boards as one release. You can monitor a cross-project release from your timeline in the same way that you can a single-project release. Learn how on the Track releases from your timeline page.
You can also align the dates of releases contained in a cross-project release so they all finish at one time. This is helpful for converging and coordinating releases from several different work streams. Learn more about how to align multiple releases on the Align cross-project release dates in Advanced Roadmaps page.
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.
Was this helpful?