How to update a workflow that is used by a scheme that is shared by 50 projects?

[Sorin Sbarnea (Citrix)]

It seems that I reached a moment where it seems almost impossible to update an workflow because it is used by 50 project.

I need to add a new transition to the Closed state and jira does not allow me to do this using Draft edit, is telling me that you cannot add transitions if the state does not have any (final).

Now, the usual workaround is to Copy the workflow do the edit and reasing it. BUT, you have also to copy the Workflow Scheme in order to do this and my Workflow schem is used by >50 projects.

It is almost impossible to go to each project and switch the workflow scheme to the new one, that's insane.

[Timothy · Accepted solution]

I wonder whether this is the feature that will help you:

https://confluence.atlassian.com/display/JIRA/JIRA+6.0+Beta+1+Release+Notes#JIRA6.0Beta1ReleaseNotes-Betterworkflow

But yea, overall, I think you would be stuck with what you have now.

[Sorin Sbarnea (Citrix)]

Yes, that's a good enough reason for switching to Jira 6.0 as soon as possible. Just hope the release will came sooner.

[Andrei [errno]]

we wrote a Selenium script to update Workflow Schemes for 40+ projects. not ideal, but worked well...

another option that might work in pre-6 JIRA : https://bobswift.atlassian.net/wiki/display/JCLI/Documentation#Documentation-updateProject

[Adam Saint-Prix]

+1 to trying the JCLI route. Probably the quickest, cleanest approach. Usual caveats apply (test thoroughly, backup, do off-hours, etc.)