Apps are required to migrate to Atlassian AccountID and remove legacy user references (username and user key) by 29 March 2019. For more background on why - please see our first post .
Understanding migration status
We are tracking use of the apiMigrations flag in the Connect App descriptor as a way to understand developer readiness to deprecate username and user key from our REST APIs. This flag serves as both a mechanism to test the new API behaviors (when set to gdpr:true), and a communication tool to signal when/where you are blocked (when set to gdpr:false).
Today, we have 38 apps that have signaled that they are ready for the deprecation, 2 that have signaled they are blocked, and ~700 that have not indicated their status. In order for us to understand where you are with migration to accountID and use that information to effectively communicate with our product teams we need you to signal your status using the “opt In mechanism”.
Atlassian Marketplace Requirements
For cloud apps that indicate that they are storing personal data, there is an additional requirement to implement the personal data reporting API. We’ve updated the messaging in Atlassian Marketplace to make it clearer that this is a requirement for apps with cloud versions only.
Recently closed issues
- Jira and Confluence webhook bodies now contain accountID and account type.
- Jira and Confluence have new migration APIs that are unaffected by the 29 March 2019 deprecation. (See here for Jira: /rest/api/3/migration) We will provide a link to the Confluence documentation soon.
- Testing Profile Visibility Controls - If you are ready to start testing profile visibility controls, please raise a ticket in our Developer Support Help Desk here . We are not quite ready but will provide you with more details on when testing will become available and what you should expect to be able to test.
Items in progress
Conversion of stored CQL containing legacy user references to accountID - The Confluence team is aware that this is an issue, however, have de-prioritized this work due to the amount of remaining work to prepare for profile visibility controls. We recommend using the new migration API provided by Confluence to transform CQL containing old user references to accountID.
Email address hidden from public by default - Email address will be hidden from public by default which means that the email address will no longer be provided to you through our product APIs for the majority of users. Users will need to manually adjust their profile visibility control settings in order to provide access to email. We recognize that for some of you this restricts core functionality. We intend to enable access to email for approved use cases only. We are working on guidelines and a Service Desk system to allow you to apply for access to an API that will provide access to email address. The API is being worked on now and should be available 15 March 2019.
Regarding the issue with the Jira PD Cleaner recognizing issue entity property aliases, the Jira team is currently working on this issue and expects the work to be complete on 28 February 2019.
Regarding the issue with ACJIRA-1625 , the Jira team is working on this and expects to ship next week.
Jira does not have an API to edit workflows (ACJIRA-1718) - the Jira team is working on this and expects the API to ship next week.
JQL when transformed using the PD cleaner becomes un-readable - We are working on a new UI component that will display the user’s current name in JQL rather than the accountID. We will provide more information on when this expects to ship next week.
We realize this is a large amount of work to complete in a short timeframe. We appreciate you working with us through this process to deliver a more trusted experience for our customers.
If we’ve missed anything preventing you from completing the migration, please comment below.