Unable to Save Workflow Schemes when associated with Projects moved to Trash

Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.

Summary

When you try to modify or publish the workflow scheme, you may come across a situation where it tends to get stuck on 'Step 1 of 2: The current status of each issue needs to be changed so that it is compatible with the new workflows.'

Diagnosis

The validation starts by reviewing the projects associated with the workflow scheme and determining whether all the projects are active or if any of them have been moved to Trash or archived (if you have a premium subscription).

Cause

The main cause for this issue is that it occurs when you have projects that are moved to trash being associated with the specific workflow scheme. Please note that the archived project does not affect this issue but only the projects moved to the trash.

Solution

You may have to either restore the projects moved to the trash or delete them permanently in order to modify and publish the draft of the workflow scheme.

Updated on March 13, 2025

Still need help?

The Atlassian Community is here for you.