The major changes that Atlassian is making to the Jira REST API on top of which all apps are built, including JMWE for Jira Cloud, will impact some or all of your workflows. Though GDPR compliance was the primary reason for the changes, they will affect customers across all countries, not only those located in the European Union.
In a nutshell, Atlassian is replacing the username and user key identifying attributes with a single, opaque accountId identifier. Jira Admins need to make changes to some of the Jira Misc Workflow Extensions (JMWE) post-functions to avoid breaking the workflows. We have covered the "breaking" changes and what you must do to ensure continuous workflow processes in this documentation page.
With the latest JMWE for Jira Cloud 1.1.12-AC release comes a helpful tool for automating and simplifying the required changes to JMWE for Jira Cloud workflows.
We developed a new tool to help you easily identify and implement all the updates you now need to make to your workflows. Here is what the GDPR Migration Tool does:
The GDPR Migration Tool is available to all JMWE for Jira Cloud customers at no cost. It can be accessed from the Apps section of the Jira administration pages, alongside other JMWE administration pages such as the JMWE Logs.
NOTE: For more information on the required changes, read this documentation page. The rollout dates of the API changes might still be changed by Atlassian, and we'll update our information accordingly - we highly recommend you "WATCH" the documentation page for updates.
Followup: One of our customers has asked whether there are any performance issues during the automatic upgrade, whether downtime is required, or any impact on running workflows or users. The answer is: there is no downtime related to using automatic migration, which takes only seconds. Users will still be able to use Jira normally, even during these few seconds.