Jira is getting a fresh new look and navigation

We’re in the process of rolling out these changes and the documentation may not match your experience. Bear with us while we update it to reflect the new changes. More about navigating the new Jira

Troubleshoot warnings in Unsaved changes modal

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

In the Unsaved changes modal, you may see warning icons in the far left column. We recommend resolving before saving changes to Jira Software.

This work item has been added to an active sprint

If you add or remove a work item from an active sprint, you’ll see a warning in the Unsaved changes modal informing you that this will change the scope of the sprint.

A warning that you'll see in the Review Changes modal in Advanced Roadmaps in Jira Software Cloud

There’s no resolving this work item as it won’t break your plan, but it’s a heads up that sprint capacity will be affected.

Required custom fields in Jira Software work items

If your Jira Software work items have required custom fields, but these fields weren’t added to your plan, you'll see a warning. Since these fields are required, you’ll need to either add them to your plan or turn off the required field in Jira Software.

Custom fields not supported for work types or projects in plan

If you set a value for a custom field that hasn’t yet been set up in Jira Software, you won’t be able to save this change from your plan. If you need this change to be saved, ask your Jira Software admin to configure this custom field in your instance.

Child work items not saved to Jira Software

If you’ve created child work items in your plan, the parent work item needs to be saved in Jira Software as well. Since the child work item is dependent on values inherited from the parent, the child work item can’t be saved on its own.

Still need help?

The Atlassian Community is here for you.