Creating releases

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

When creating releases in a plan, you have the choice of creating either a project release or a cross-project release.

Project releases are good to start with, especially if you're still in the early stages in planning work for your team. You can keep your releases as specific as you need them to be to their corresponding Jira projects. As your plan becomes bigger, and you add more projects to it, you may want to start considering creating cross-project releases. 

Cross-project releases help you organize multiple releases across different Jira projects — think of it as grouping together related releases into a single cross-project release. You can also align the dates of the related releases, helping you organize and prioritize work for your teams.

Note that if you've set releases for your issues in Jira, these releases will also be displaying in your plan.

If there are no releases existing in your plan yet, you'll be prompted to start creating a release.

Sample plan, with no releases added to it yet

Creating a project release

When saving a project release to Jira, the release becomes available for use in Jira as well.

To create a project release:

  1. In the releases view of the plan, go to the project for which you want to create a release.
  2. Click Create release next to the project name. This will display the 'New release' dialog.
  3. Give the new release a name.
    Note that no two releases in the same project can have the same name.
  4. Add a description for the new release.
  5. For the start date, choose from one of the following options, and then set the date:
    • As early as possible: When auto-scheduling the plan, the release will start as soon as there are available teams to work on the issues in the release.
    • Fixed date: You can set a preferred date for the start date.
    • Relative to previous release date: You can specify the gap of time that you want to allocate after the previous release finishes, and work on the new release starts. For example, you may want work for the beta release to start 1 day after work for the alpha release is completed.
  6. For the release date, choose one of the following options, and then set the date:
    • After all issues are completed: The release date will be dependent on when all the issues in the release will be completed.
    • Fixed date: You can set a preferred date for the release to be completed. In the timeline, the release icons will turn red for overbooked releases — when this happens, you may want to consider moving issues to future releases.
  7. Click Create. The new release will be added to the plan.
  8. Save the changes by doing the following:
    1. Click Review changes. The 'Review changes' dialog will display, with all changes selected by default.
    2. Make sure the checkboxes for the release changes are selected, then click Save selected changes in Jira.

    You need the  Portfolio for Jira user permission to save changes in Jira.

Creating a cross-project release

Cross-project releases are local to and are only used in Portfolio for Jira. This means that these releases are not saved to Jira at all.

For example, let's say you've already created a project release and a cross-project release. You then add the project release to the cross-project release, and then save these changes to Jira. This effectively saves the project release in Jira, but not the cross-project release.

To create a cross-project release:

  1. In the releases view of the plan, go to the cross-project releases section.
  2. Click Create at the top of the cross-project releases section. This will display the 'New cross-project release' dialog.
  3. Give the new release a name.
  4. Choose the project and the corresponding release that you want to add.
  5. Click Add release. This will add the project release to the list of cross-project releases below. Repeat the previous step and this step, to add as many releases as necessary.
  6. Once you're done adding project releases, click Create.
  7. Save the changes by doing the following:
    1. Click Review changes. The 'Review changes' dialog will display, with all changes selected by default.
    2. Make sure the checkboxes for the release changes are selected, then click Save selected changes in Jira.

    You need the  Portfolio for Jira user permission to save changes in Jira.

Since cross-project releases are local to and are only used in Portfolio for Jira, only the releases changes are effectively saved to Jira.

Last modified on May 7, 2019

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.