Atlassian is making changes to Jira Cloud to provide users with more control over their profile information - both in response to recent changes to data privacy legislation (i.e. GDPR) and as part of a broader effort to improve customer trust. These efforts include major breaking changes to the Jira REST API on top of which all apps, including JMWE for Jira Cloud, are built.
Despite our best efforts to makes the changes transparent to our customers, they will have an impact on your workflows, and you will need to make changes to some of the JMWE workflow post-functions you have configured.
Atlassian pushed back once again the deployment of the first wave of breaking changes ("Phase 2" below) to June 11. You have therefore up to June 11 to make the changes required for Phase 2 (see below).
Atlassian pushed back the deployment of the first wave of breaking changes ("Phase 2" below) to June 2 at the earliest. You have therefore up to June 2 to make the changes required for Phase 2 (see below).
The Jira Cloud bug that prevented some JMWE post-functions from being listed by the GDPR Migration Tool is now fixed. The tool will now list all the required changes.
|title||May 8th update|
Automatically find and fix post-functions affected by Atlassian's GDPR changes
Our new GDPR Migration Tool helps you identify and implement the changes required by Atlassian's
- Offers a one-click migration option that applies some of the required changes automatically;
- Lists all the JMWE post-functions in your workflows that require changes
- Allows you to edit these post-functions directly from the tool
|title||April 26 update|
The GDPR Migration Tool is available from the Apps section of the Jira admin. You can also navigate to it via <Your base URL>/plugins/servlet/ac/com.innovalog.jmwe.jira-misc-workflow-extensions/gdpr-checker.