Weekly GDPR API status development - May 31

Update on the roll out of new Bitbucket Cloud, Jira Cloud and Confluence Cloud APIs

Bitbucket APIs The new Bitbucket APIs have been rolled out to 100% of Bitbucket instances and apps.

Jira APIs The roll out percentage remains at ~56% of Atlassian Connect apps for Jira. All of the apps that have opt’d in so far have signaled gdpr:true . We have paused the roll out to address remaining blockers (e.g. ACJIRA-1768 ). We expect to resume roll out next week. We may begin rolling out to apps that have not set gdpr:true or gdpr:false at that time. If you are still signaling gdpr:false please note that we intend to shut down the whitelist and complete roll out to apps and direct rest calls on 2019-06-11T14:00:00Z.

Confluence APIs the target roll out date for Confluence APIs is now 2019-06-11T16:00:00Z.

Next up: Profile Visibility Controls

The target date for launch of profile visibility controls is now June 11, 2019 (Sydney) .

The testing window has now closed. If you’ve already had an instance configured for testing, the configuration has temporarily been turned off.

As a reminder, the API roll out mentioned above will not affect the profile data returned thru user objects. If you’ve tested the API behaviors using the Jira REST header x-atlassian-force-account-id:true and/or Confluence query parameter privacyMode=true and the Atlassian Connect descriptor flag gdpr:true , then you should be familiar with the changes that will start rolling out next week.

Following the roll out of the new APIs, we intend to release a new feature for Atlassian Account which may change the data returned thru user objects. Certain fields like timezone and email address may be hidden by a user and not return in the user object. Additionally, the user may decide to show only public versions of their name or avatar.

All of these changes including the default settings are documented in these guidelines .

If your app requires use of email address to provide core functionality, please raise a request to access the email API. Should you use the email API without raising a request your app may be prevented from being installed .

Thank you

As always, thank you for working with us through these changes. Its been a large amount of work to complete in a short timeframe and we appreciate you helping us deliver a more trusted experience for customers.


Hi! It appears some change was made to the Confluence API on June 5th (yesterday) now causing this error for our app:

Add-on 'app' disallowed to impersonate the user because 'no valid active user exists'

This is a new error which is suddenly appearing for us using ‘act as user’ for the REST call ’ Update space’ on the Confluence API.

We have not been able to determine why or what is suddenly causing this.

Can we see a change-log of the server and specifically the APIs?

Any hints would be appreciated.

(We’ve been struggling recently to keep up with all of the errors being introduced to the fabric editor and APIs.)

@brendan, I have raised this as CONFCLOUD-66808. Please watch that issue for updates.