See how Jira and Innovalog's workflow automation can help
3 minutes reading time (630 words)

Important changes that affect Jira Cloud workflows, and how to fix them before they break

New privacy changes might break your Jira workflows

Starting on April 29th, in a continuous effort to improve customer trust and address all EU General Data Protection Regulation (GDPR) requirements, Atlassian is making very important changes to Jira Cloud that will affect (break!) some of your workflows. This affects all Jira Cloud customers.

Atlassian will be changing the way Jira Users are exposed through its APIs. In particular, they are replacing the username and user key identifying attributes with a single, opaque accountId identifier. These changes impact user information received from Jira, as well as user information sent to Jira.

They are also hiding, by default, many other user attributes, such as the email address, full name, avatar, etc. You can make these attributes available again within your Jira Cloud instance, however, individual users may update their privacy settings to "hide" their email addresses (which will impact your scripts, if any). Going forward, only the accountId will serve as a reliable way to identify users.

Despite our best efforts to make these changes transparent to our customers, they will impact your workflows - Jira Admins will need to make manual changes to some of the Jira Misc Workflow Extensions (JMWE) for Jira Cloud post-functions.

For the past 6 months, our developers have been working closely with the Atlassian team to ensure you have an opportunity to update your workflows without breaking your Jira instance. For a period of time, Atlassian will offer a temporary compatibility API that will allow JMWE for Jira Cloud to continue supporting most of the existing post-function configurations, even if they still refer to usernames and user keys.

Here is how to identify and fix affected workflows

These changes will impact some or all of your workflows, including post-functions offered by JMWE for Jira Cloud

You will have to review your workflows and make changes to some or all JMWE for Jira Cloud post-functions. In a nutshell, in post-functions referencing usernames and user keys, these properties must be replaced with an accountId property. To correct issues in some post-functions, all you need to do is "edit" it and then "save", without making any changes - this will simply store the reference to the user as an accountId instead of a username.

 Timeline of changes:

Phase 1: April 21, 2019

We have released a new version of JMWE for Jira Cloud. It is fully compatible with all your existing workflows, but enables you to identify the post-functions that need changes and make these changes ahead of the "breaking" deadline.

Phase 2: May 16, 2019 (extended from previously-reported April 29)

Atlassian will deploy the GDPR "breaking" changes mentioned above.

However, through a compatibility API, JMWE for Jira Cloud will continue supporting most of the existing post-function configurations, even if they still refer to usernames and user keys. The only post-functions that will stop working are those that include a Nunjucks template that compares a username to a constant string.

NOTE: Comparing the value of a user-type field with a specific user must be fixed before May 16th (updated from April 29th). 

Phase 3: To be announced by Atlassian(at the end of June, 2019 or later) 

Atlassian will remove the compatibility API introduced in Phase 2. At that point, all your post-functions will need to have been updated as described here.

Fix your workflows automatically with the new Migr...
Conditions/Validators for Jira Cloud [now availabl...

Related Posts



No comments made yet. Be the first to submit a comment
Sunday, 04 December 2022

Captcha Image