Save changes made in a 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 Plans administrator permission as well as permission to edit the project in Jira.
As you build your plan, changes to work items or Teams are in a draft state until you’re ready to save them. This allows you to explore different planning outcomes without effecting existing work items. 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 by title. If there’s multiple updates to a work item, the number of changes shows in the What changed column. Select the field in this column to view all of the changes made to that work item.
To save work done to date, select the changes you’d like to save and click the Save changes button. You can also filter changes in the Unsaved changes modal.
Any change remains visible on this screen until you:
save it or
discard it by selecting the change, then Discard selected changes
You can also send notifications to those watching work items by using the Send update notifications checkbox in the lower left corner.
Changes you can find in this modal
The Unsaved changes modal will display following change types made inyour 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. Changes will remain in the Review changes modal until they are saved or discarded.
If you are planning with multiple scenarios, these changes will be applied to all scenarios in your plan.
Updates to work items
create a work item in your plan
change a work item:
estimate
team assignment
summary
scheduled dates or sprint assignment
value in a custom field
remove a work item 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?