As an admin, I am using a simple workflow which has suggested by jira - Now I want to change the workflow - so I go to projects--> workflow - change it - all the issues got migrated to the new workflow - Now I switch back to the previous workflow - In this scenario, all the issues got migrated to the previous workflow, but all the issue's status shows 'Backlog' with the label 'Done' even it got done earlier.
I will share the screenshot
Jira can only take a minimal approach to migrating data on workflow changes. It can't know what we might be doing when we are changing them, and asking for every last possible alternative would be massive. So when you change a workflow, it does the minimum.
For each status in the old and new workflow, there are only two possibilities
Now, when you go "back", Jira has no way to know what status you might want to take on, so it does the same routine. Although the previous-workflow status is recorded in the history, the issue may have moved on, and there is no way that Jira can know whether you want to go back to the original status, retain the current one (assuming it is in both workflows) or keep the latest. It can't work out what you need, so it does the same simple non-historical minimal change - retains the status when it can, and asks you if the current status is not in the target workflow.
Hi everyone! My name is Jenny, a Product Manager at Atlassian. After launching Team @mentions in Confluence, we heard a lot of positive feedback from customers that they love how easy it is to @men...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events