Configure releases with plans in Jira

5 min

By the end of this lesson, you'll be able to:

  • Configure releases for one or multiple spaces in plans

Create a release in a plan

Releases are target deadlines for sections or versions of your work. Releases appear as an icon on the top of your timeline.
👇This is what a release looks like in a plan’s timeline.
A Jira plan timeline with a marker showing a scheduled release date.
To create a release:
  1. In the plan navigation, click Releases.
  2. Next to the space you want to add a release to, click Create release.
  3. Enter a name, dates, and description for the release.
  4. Click Create.

Configure dates for a release

Releases have two dates: a start date and a release date. These dates determine the length of the release. You can use different information to determine what the start date and release date are.
👇Click the boxes below to explore the options for the start date.
👇Click the boxes below to explore the options for the release date.

Create cross-space releases

You can use cross-space releases to track the progress of several spaces working toward a shared release.
👉 For example: Two teams are working on a mobile app. You added releases from both iOS and Android into the Mobile 1.0 cross-space release.
To create a cross-space release:
  1. In the plan navigation, click Releases.
  2. Click Create cross-space release.
  3. Enter a name for the release.
  4. In the Linked releases section, select one of your spaces and its corresponding release.
  5. Click Add release.
  6. Add other spaces and releases as needed.
  7. Click Create.
By default, single-space releases contained within a cross-space release can have their own dates. If you want all single-space releases to converge or begin simultaneously, you can align releases using start or end dates.

In Jira, cross-space releases are only used in plans. This means that these releases are not saved to Jira at all. They are used for planning purposes only.

How was this lesson?

Community

FAQsForums guidelines
Copyright © 2026 Atlassian
Report a problemPrivacy PolicyNotice at CollectionTermsSecurityAbout