Test Management for Jira Cloud

Rest API Changes for GDPR Compliance

On 29 April 2019, Atlassian made changes to the data that they supply via their API in order to be GDPR compliant.

Please read below to learn about changes to REST API and the importing/exporting of user data that Test Management for Jira (TM4J) Cloud is introducing in conjunction with these changes.

If you have any questions, please raise a ticket through our Support Desk, and we’ll get back to you as soon as possible.

REST API Changes

Previously, API definitions used Atlassian User Keys to identify users. This has been deprecated by Atlassian and was removed on 29 April 2019.

Atlassian Account IDs have replaced User Keys to represent users, so TM4J Cloud has also made this change by replacing any fields that require User Keys with Account IDs.

To interact with the API going forward, you must use these new fields. For example, if you have written a script that uses a userKey field, such as owner, you must change it to use a corresponding accountId field instead, such as ownerId.

For more detailed information on API changes, please view our API documentation.

Import and Export Data

We have added a new field named Owner (Account ID) to all data exported from Test Management for Jira, and, in addition, the import provides this extra field for field mapping.

If you wish to import any previous backup data after 29 April 2019, you will need to export your data once again to make sure you will have the new Account ID field included in your exported file.

Find Your Atlassian Account ID

To find your Atlassian Account ID, go to your profile in the Jira menu.

100%

Your Account ID appears in the page URL.

100%

If you have any questions, please raise a ticket through our Support Desk, and we’ll get back to you as soon as possible.