Jira GDPR Changes

(warning) NOTE: Upcoming Mandatory Upgrade

Last Updated:  

(lightbulb) Please be aware that Atlassian and Zephyr may continue development to implement GDPR changes up until the deprecation date. This means that if either vendor makes additional changes, subsequent Tasktop upgrades may become necessary. We will continue to update this page with up-to-date information regarding upgrade path.  We recommend that you continue to monitor this page for details.

Atlassian recently introduced a number of changes to their products and APIs in order to improve user privacy in accordance with GDPR.

You can see details for Atlassian and Zephyr at the links below:

These changes will require all Tasktop customers integrating Jira Cloud or Zephyr Cloud to upgrade their instance of Tasktop Sync or Tasktop Integration Hub based on the instructions below:

  • Jira Cloud users must upgrade their Tasktop instance to one of the following versions by April 29th, 2019*
    • Tasktop Integration Hub 19.1.3+ or Tasktop Sync 4.17.3+ released on or after January 30th, 2019

    • Service Releases on 18.1-18.4 or 4.13-4.16 released on or after February 6th, 2019

  • Zephyr Cloud users must upgrade their Tasktop instance to one of the following versions by May 31st, 2019*
    • Service Releases on Tasktop Integration Hub 18.2-19.1 or Tasktop Sync 4.14-4.17 released on or after March 19th, 2019

What’s changing?

Atlassian is changing user identification (previously a 'username', such as 'tasktopuser') to a user 'account ID' (an alphanumeric string such as 'abc-123-def-456'). The API deprecation will be completed by April 29, 2019*.  Zephyr will deprecate the old API by May 31, 2019*.

Do I need to upgrade?

If your organization does not have integrations with Jira Cloud or Zephyr Cloud, you do not need to upgrade your Tasktop product. Integrations with the On Premise versions of these products will not be impacted. If you are uncertain whether or not this upgrade applies to you, please contact Tasktop Support to confirm.

If you are considering adding Jira Cloud or Zephyr Cloud to your integrations anytime soon, we’d recommend you follow the recommended upgrade path below as well.


Are you integrating

Jira Cloud Artifacts?

Are you integrating

Zephyr Cloud artifacts?

Upgrade Path
(tick) (error)

Upgrade to one of the following versions by April 29, 2019*:

  • Tasktop Integration Hub 19.1.3+ or Tasktop Sync 4.17.3+ released on or after January 30th, 2019

  • Service Releases on 18.1-18.4 or 4.13-4.16 released on or after February 6th, 2019


(lightbulb) Please be aware that Atlassian and Zephyr may continue development to implement GDPR changes up until April 29th, 2019*. This means that if either vendor makes additional changes, subsequent Tasktop upgrades may become necessary. We will continue to update this page with up-to-date information regarding upgrade path.
(error) (tick)

Upgrade to one of the following versions by May 31, 2019*:

  • Service Releases on Tasktop Integration Hub 18.2-19.1 or Tasktop Sync 4.14-4.17 released on or after March 19th, 2019


(lightbulb) Please be aware that Atlassian and Zephyr may continue development to implement GDPR changes up until April 29th, 2019*. This means that if either vendor makes additional changes, subsequent Tasktop upgrades may become necessary. We will continue to update this page with up-to-date information regarding upgrade path.

(tick) (tick)

Upgrade to one of the following versions by April 29, 2019*:

  • Service Releases on Tasktop Integration Hub 18.2-19.1 or Tasktop Sync 4.14-4.17 released on or after March 19th, 2019


(lightbulb) Please be aware that Atlassian and Zephyr may continue development to implement GDPR changes up until April 29th, 2019*. This means that if either vendor makes additional changes, subsequent Tasktop upgrades may become necessary. We will continue to update this page with up-to-date information regarding upgrade path.

(error) (error) If you are using On Premise versions of Jira and Zephyr or are not integrating artifacts from Jira or Zephyr at all, there is no required upgrade path - users may upgrade or not upgrade as they choose.

*Note that the Jira deprecation date was originally March 29, and has been delayed as of March 5, 2019.  Zephyr's date has been pushed back from April to May per https://zfjcloudgdpr.docs.apiary.io/#reference.

How do I upgrade?

We will notify you when the releases supporting these changes become available. At that time, your Tasktop product administrator will be able to access the upgrade via their my.tasktop.com account or by contacting Support. 

Please review upgrade details below.  You can also review upgrade details in our Release Notes and find additional details on the Jira connector in our Connector Docs.

What should I be aware of when upgrading? 

Tasktop Integration Hub:

  • The user account associated with the Jira Cloud repository connection must have the 'browse users and groups' permission granted.

  • Any existing Jira Cloud collections with default person reconciliation that rely solely on Jira and the target repository having identical usernames will no longer work. A person reconciliation extension will be required in such cases. Behavior for Jira On Premise is unchanged.

  • Any existing extensions for Jira Cloud that utilize the person-username field to search or map from Jira must be updated to use a different field such as person-email, as Jira has replaced the username field with a user account ID to comply with GDPR.  Extensions for Jira On Premise will not need to be changed.

  • If there are field mappings that map Jira Cloud person fields to a string field (including mappings for Enterprise Data Stream), be aware that those will now flow the Jira account ID (i.e. an alphanumeric string such as 'abc-123-def-456'), rather than the Jira username (a readable field such as ‘TasktopUser’).  We recommend changing the transform to 'Person to String (Display Name)' in these scenarios.  Behavior for Jira On Premise is unchanged.

  • Gateway payloads sent to Tasktop using person(s) fields may need to change to send appropriate data (for example, e-mail instead of username).  If using gateway collections with Jira Cloud, please review payloads upon upgrade and update as needed, or consider using an extension to ensure the correct data is sent.


Tasktop Sync

  • The user account associated with the Jira Cloud connection must have the 'browse users and groups' permission granted.

  • The auto-comment user name will need to be manually changed to accountid for any existing and new Jira Cloud mappings. By default, Sync is using the username from repository settings as auto-comment user when creating new mappings. If repository settings do not specify username (for example, when email + API token authentication is used), the auto-comment user field will be empty. In either case, in order to be used by Sync, it will need to be replaced with a valid accountid. Behavior for Jira On Premise is unchanged.

  • Any task mappings for Jira Cloud that map person attributes without using a person-mapping.xml file will no longer work. A person-mapping.xml file will be required. Behavior for Jira On Premise is unchanged.

  • All usernames in the person-mapping.xml files related to Jira Cloud mappings will need to be replaced with Jira accountIDs. Behavior for Jira On Premise is unchanged.

  • Any existing person-mapping.xml files with field-based person mapping using Jira Cloud’s person-id or person-username fields will no longer work. These will need to be changed to use a different Jira person field, such as person-email. Behavior for Jira On Premise is unchanged.

  • The mapping scripts will be passed the Jira accountID as an argument when mapping Jira Cloud users, and will need to be updated accordingly. Behavior for Jira On Premise is unchanged.

  • If there are field mappings that map Jira Cloud person fields to a string field, be aware that those will now flow the Jira account ID (i.e. an alphanumeric string such as 'abc-123-def-456'), rather than the Jira username (a readable field such as ‘TasktopUser’).  A custom caster script can be used to flow the display name to a string field.   Behavior for Jira On Premise is unchanged.