Troubleshoot warnings in Unsaved changes modal

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 issue has been added to an active sprint

If you add or remove an issue 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.

There’s no resolving this issue 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 issues

If your Jira Software issues 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 issues 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 issues not saved to Jira Software

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