My workflow ends with STATUS DONE. But, users are selecting DONE and then changing their minds. But, there is no option to go back.
When I edit the workflow, I try to add a transition from DONE to a previous step, but I get an error message that I cannot make that change to a workflow in DRAFT. But, I cannot edit the workflow unless it is in DRAFT. Makes no sense.
How do I simply add an option for the user to go back to the previous step?
In some cases, you will have to make the workflow inactive, not just a draft. Copy the workflow to a new version, make the changes there and then update the workflow scheme with the new version of the workflow.
Thank you, Jobin. I was able to make the workflow changes as you suggested. But, when I go to publish the workflow scheme, on step 1 of 2 I get a big warning that all the statuses need to be changed in order to be "compatible" with the new workflows. There are a bunch of workflows that are not mine and I am worried that the status for other groups will get changed for some reason. Plus, my workflow change did not add or delete any statuses, so I don't know why the message even comes up.
Any suggestions or assurances?
It sounds like you have made significant changes to the workflow scheme, probably inadvertently.
Go back to the project and look at the "workflow scheme", just get its name for now.
Now go to Admin -> issues -> workflow schemes, find it and make a copy.
Go into the copy and find where your old workflow is used. Replace it with the edited copy of the workflow.
Now go back to the project and change the workflow scheme to the new one.
This should preserve all your status for all issue types and not ask you about migrations at all.
No significant changes. I just added an updated version of an existing workflow. But, I did not first remove the old workflow. It just replaced it with the new one when I selected the one issue type that it was associated with.
Could that be the problem? I need to remove the old workflow first and then add the updated workflow version?
There are many other workflows in this scheme but I did not touch any of them.
No, I meant significant change to the workflow scheme, not the workflow.
The workflow is the process flow. The workflow scheme tells a project what workflow to use for each issue type within it.
You can't associate a workflow with a project or issue type directly, you have to do it with a scheme.
It turns out the warning that worried me was just a generic warning and I was taking all of the appropriate steps. Upon executing steps 1 and 2, everything got updated (very quickly because I never changed any of the existing statuses, just added a workflow) and I now can recover from an accidental DONE status change.
Thank you, everyone, for your suggestions. They all helped.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hi, everyone! Molly here from the Jira Service Desk Product Marketing Team :). In the spirit of this month's august-challenge, we're sourcing stories of Jira Service Desk activation fro...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs