Apps are required to migrate to Atlassian AccountID and remove legacy user references (username and user key) by April 29, 2019 (Europe: Paris), April 29, 2019 (America: Los Angeles). 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 you are blocked (when set to
Today, we have 66 apps that have signaled that they are ready for the deprecation, 18 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”.
Learn more about how to properly use this flag.
Additional note on opt’ing into the new API behaviors
The flag described above controls Atlassian Connect behaviors. When opt’d in
x-atlassian-force-account-id’:true. This header is also required to transform change logs from username to accountID. The query parameter for Confluence is
Recently closed issues
Jira webhooks missing accountId and account type - Jira has communicated that this is rolling out this week and should be complete by end of week. See ACJIRA-1674.
User mentions in Wiki Markup not working with expected format - User mentions in Jira require a prefix prior to accountID in order to work correctly. New user references will be saved in this new format, however, historical references not stored in Jira will need to be migrated. Jira will not commit to facilitating this migration prior to the deprecation of username and user key. See ACJIRA-1715
Email address hidden by default - Check out our newly released Guidelines for requesting access to email address. The Email API is still being worked on (see In Progress).
Items in progress
AccountID in JQL
statusbyclause does not work - Jira is working on this and have a fix in place but not released yet. This may be resolved before our next weekly status update. See ACJIRA-1625. An additional issue was raised specifying componentsLeadByUser() method. The work to fix this bug is in progress. We do not yet have an estimated fix date yet. See ACJIRA-1704.
Jira user picker REST API missing account type - Same as above (fix in place but not released yet). See ACJIRA-1686.
Jira post function /triggered calls missing accountID and account type - This issue was split from the above. The Jira team has is preparing to work on this issue. The estimated fix date is March 20, 2019 (Europe: Paris), March 20, 2019 (America: Los Angeles). See ACJIRA-1722.
Jira incoming webhooks missing accountId - Jira is planning to add a separate event that will use accountIds. The work on this issue has not started yet nor do we have estimates for when this will be fixed. See ACJIRA-1692.
Jira does not recognize issue entity property aliases - The Jira team is currently working on this issue and estimates this work to be complete next week. See ACJIRA-1723.
Jira does not have an API to edit workflows - The Jira team is working on this and expects the work to be complete March 19, 2019 (Europe: Paris), March 19, 2019 (America: Los Angeles). See ACJIRA-1718.
JQL transformed to remove legacy user references and replaced with accountID are un-readable - We’re building a JQL Editor Dialog component that will display the user’s current name in JQL rather than the accountID. This work is in progress and we expect this to ship March 15, 2019 (Europe: Paris), March 15, 2019 (America: Los Angeles). See ACJIRA-1710.
Email address hidden by default - The Email API is being worked on now and should be available on March 15, 2019 (Europe: Paris), March 15, 2019 (America: Los Angeles). See ACJIRA-1726
Jira PD Cleaner converting user strings that are not exact usernames to ‘unknown’ - This issue was raised in ACJIRA-1712 but now is being tracked in ACJIRA-1725. We do not have estimates for how/when this will be fixed.
Confluence documentation for new REST endpoint for migrations - Jira and Confluence have new migration APIs that are unaffected by the 29 April 2019 deprecation. (See here for Jira: /rest/api/3/migration ) The endpoint for Confluence is ‘/wiki/rest/api/user/bulk/migration?username=’. Documentation is not currently available. We will provide a link as soon as it becomes available.
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 to set up developer environments but this guide will describe how testing will work and what you can expect once privacy controls are turned on.
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.