This question is in reference to Atlassian Documentation: JIRA Miscellaneous Workflow Extensions (JMWE) removal from JIRA Cloud
I am sure I have used these a lot and this would take many hours to correct if it isn't done automatically.
How can I tell which workflows in my system will be affected?
Also, is this going to be one of those nickle and dime paid versions like the Timesheets debacle?
The workflows store the usage of the add-ons as pointers to the functions in use. They will only fail when the users trigger the transition that tries to use them.
However, as stated in the doc, the ones that are moving into JIRA will migrated automatically, and for the ones that aren't, you can install the new JMWE add-on and they will be migrated too.
If you don't want to use the new JMWE though, it's a bit of a pig to find them without ploughing through every workflow by hand. I cheat a bit - download a backup copy of the whole system, and expand it to get the raw xml out of it. You can then search it with text for the class names of the addon (it'll be something like com.innovalog.jmwe), and that will tell you all the places it's been used.
So, installing the new version of the add-on will automatically convert all remaining functions not supported by JIRA? It does seem like users should be provided a report that identifies affected workflows. Surely, Atlassian could automate this in a fraction of the time it will take all of us to comb through our exported xml?
Not for the functions that will rely on the new add-on. The link appears to say twice that those must be done manually:
"You will be able to install this add-on on your instance and migrate to the replacement post-functions."
"You can install this add-on from the Find New Add-ons page in the JIRA administration section of your JIRA Cloud instance. Then you can migrate your existing workflows to use the same post-functions as provided by the new add-on."
I'm not concerned about any functions in particular. I'm concerned about having to track any of them down across dozens of workflows and hundreds of transitions. I appreciate @Nic Brough [Adaptavist] providing the shortcut, but I feel that Atlassian should be making it easier on any of us who might need to migrate to a new add-on – beginning with an automatic way to know if the new add-on will be required.
Yes, the trick I use is better than nothing, but it's still less than ideal.
With workflows, I'd like something that can dump out a list of all usage of <string> within them - that's got more uses than just looking for classes for add-on changes/updates.
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