Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to automatically update JMWE for Jira Cloud post-functions breaking due to Atlassian API changes

Hello Atlassian Community! I am with Innovalog, and if you are a JMWE for Jira Cloud customer, I hope you’ll find this article useful.

As you might already know, Atlassian’s changes to the Jira REST API (on top of which all apps, including JMWE for Jira Cloud, are built) will impact some or all of your workflows. Atlassian is making these major changes in order to address the EU GDPR requirements. While they are important to ensure customer trust, they will, however, require you to update your Jira Cloud workflows. Our team has put a significant effort into developing the GDPR Migration Tool to make the process of finding and fixing workflows that require post-function changes simpler for you.

Here is what’s happening:

In a nutshell, Atlassian is replacing the username and user key identifying attributes with a single, opaque accountId identifier. They have provided specific information about the changes here. Jira Cloud Admins need to make changes to some of their workflow post-functions, including Jira Misc Workflow Extensions (JMWE) post-functions, to avoid breaking their workflows. We have covered the “breaking” changes in JMWE for Jira Cloud and what customers must do to ensure continuous workflow processes in 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.

Here is how to automatically find and fix workflows before they break

The latest JMWE for Jira Cloud 1.1.12-AC release includes a helpful tool for automating and simplifying updates to post-function configurations. Here is what our GDPR Migration Tool does:

  • It scans and lists all the JMWE post-functions in your workflows that require changes;
  • It allows you to edit these post-functions directly from the tool;
  • It offers a one-click migration (fix) option that applies some of the required changes automatically.

The GDPR Migration Tool is available to all JMWE for Jira Cloud customers. It can be accessed from the Apps section of the Jira administration pages, alongside other JMWE administration pages such as the JMWE Logs.

I hope you’ll find this tool useful. If you encounter any issues, please don’t hesitate to reach out to us.

1 comment

Inna Gordin
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
May 23, 2019

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. 


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events