Set up Jira Cloud
Learn how to set up Jira Cloud and integrate it with other products and applications.
Save changes made in your plan
This page refers to the advanced planning features that are only available as part of Jira Cloud Premium and Enterprise.
To save the changes made in your plan, you'll need the your plan administrator permission as well as permission to edit the project in Jira.
As you build your plan, edits to things like issues or Teams are held until you’re ready to update your issues. This allows you to explore different planning outcomes without effecting existing issues. When you’re ready, you can save edits made in your plan so that they appear elsewhere in your site. Jump to the list of changes you might see in this screen.
Changes on this screen are listed according to the Issue key. If there’s multiple updates to an issue, the number of changes shows in the What changed column. Select the field in this column to view all of the changes associated with that issue.
To save your work so far, select the changes you’d like to save. To speed up the process, filter the issues in the Review changes modal.
Any change you choose not to save remains visible on this screen until you:
save it or
discard it by selecting the change, then Discard selected changes
Lastly, choose whether you want to send notifications to those watching your issues in Jira based on their Jira notification settings using the Send update notifications checkbox in the lower left corner.
When you’re ready, use the Save selected changes in Jira button to commit your changes.
Changes you can find in this modal
In the Review changes modal, you’ll see the following changes made in your plan:
Unless you’re planning with multiple scenarios, the changes below marked with an * have no impact outside of your plan. You can save them to get rid of the unsaved changes markers in your plan, or ignore them (though they’ll remain in the Review changes modal until you decide to save them).
If you are planning with multiple scenarios, these changes will be applied to all scenarios in your plan.
Updates to Issues
create an issue in your plan
change an issue’s:
estimate
team assignment
summary
scheduled dates or sprint assignment
value in a custom field
remove an issue from your plan*
Updates to teams
Atlassian teams
Atlassian teams can be used outside of your plan as soon as they’re created. The changes related to them that appear in the Review changes modal are only important if you're planning with multiple scenarios.
create or add a new team in your plan*
change an existing team’s name, sprint capacity, or sprint length*
remove a team from your plan*
Plan-only teams
create a plan-only team in your plan
Plan-only teams need to be saved using the Review changes modal in order to promote them to Atlassian teams.
edit team membership*
change an existing team’s name, sprint capacity, or sprint length*
deleting a plan-only team*
Updates to releases
editing a release’s
name
description
dates
creating a new single-project release
creating a new cross-project release*
removing a single-project release*
To delete a single-project release, you’ll need to go to the project in which it was created.
deleting a cross-project*
Was this helpful?
Still need help?
The Atlassian Community is here for you.