• Products
  • Documentation
  • Resources

How do single-project and cross-project releases differ?

This page refers to the advanced planning features that are only available as part of Jira Cloud Premium and Enterprise.

We have a separate section for documentation about the project timeline that’s included in Jira. Go to the documentation for the project timeline in Jira.


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. Find out how to track releases from your timeline.

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. Find out how to align multiple releases.

A cross-project release is a way to align multiple single-project releases, and is only used for planning purposes in your plan. 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.


Still need help?

The Atlassian Community is here for you.