Skip to main content
Language Selector

  1. Other Languages

    (machine translation)

Planview Customer Success Center

Jira GDPR Changes

  1. Last updated
  2. Save as PDF

Last Updated: 31   |  Applicable Hub Versions: All

NOTE: Upcoming Mandatory Upgrade

(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 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 customers integrating Jira Cloud or Zephyr Cloud to upgrade their instance of Tasktop Sync or Planview Hub to any version released on or after July 30, 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'). 

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 Hub 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 customer care to confirm.

If you are considering adding Jira Cloud or Zephyr Cloud to your integrations anytime soon, we recommend you upgrade as well.

How do I upgrade?

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

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 documentation.

What should I be aware of when upgrading? 

Planview Hub

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

  • 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 Hub 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.

  • Recent changes to profile visibility settings made by Atlassian to Jira Cloud servers have impacted Hub’s ability to match persons by email address. Planview Hub versions released after July 30, 2019 contain a fix that enables Hub to match persons flowing into Jira Cloud by email address, but not out of Jira Cloud.

    To resolve this, we recommend that customers ask their Jira users to update their profile visibility settings  to allow anyone to see their email address. 

Tasktop Sync

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

  • 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.

  • Recent changes to profile visibility settings made by Atlassian to Jira Cloud servers have impacted Tasktop Sync’s ability to match persons by email address. Tasktop Sync versions released after July 30, 2019 contain a fix that enables Tasktop Sync to match persons flowing into Jira Cloud by email address, but not out of Jira Cloud.

    To resolve this, we recommend that customers ask their Jira users to update their profile visibility settings  to allow anyone to see their email address.