Since JIRA doesn't support "subtractive" draft editing of workflows, I've been trying to find ways around this.
The reason I'm trying this is because I have hundreds of projects mapped to a workflow scheme. If I did this the "right way," JIRA would iterate through all the issues in the hundreds of projects, and perform workflow verification/migration on the tickets. With million, this becomes very slow.
Another method I've been experimenting with:
This method cosmetically seems to work. Anyone ever hit this same situation?
JIRA does allow the draft editing of workflows, it's just that some things can't be done in draft because data needs to be migrated if you do it.
There's a good reason it is there - to stop you messing up your data. It's actually doing something similar to what your experimental method is doing - when you apply the new workflow, it's effectively doing bulk changes to the affected issues.
You're right about the volume - the checks and changes JIRA does is bigger than a bulk transition. But if you miss one issue, you've got a broken JIRA
On step 5 - this is risky, although it will work in theory. You've got the best method, because step 2 will ensure you've got a valid workflow. But I'd worry that any other edits you make might break it - if one step id is wrong, you've got a broken set of JIRA issues.
In short, I can't recommend your method of change, but if you keep it absolutely minimal and you're really careful, it should be ok.
I'd add two steps
5.5 - export the imported workflow again and compare it with the original export to make 100% sure that only the status you want to kill has been removed (as well as its transitions). Most importantly, no ids have been changed
7 - run the integrity checker to validate the workflows against issues. It should spot no problems if it's worked.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot