Apps are required to migrate to Atlassian AccountID and remove legacy user references (username and user key). For more background on why - please see our first post .
Update on deprecation date
Previously we’ve communicated that apps are required to complete their migration to Atlassian AccountID and remove legacy user references (username and user key) by March 29, 2019 (Europe: Paris), March 29, 2019 (America: Los Angeles). Due to the amount of remaining open issues raised by you, the Developer Community, we’ve decided to extend the deprecation notice period by 30 days. The new target deprecation date for Jira Cloud, Confluence Cloud, Bitbucket Cloud and Connect REST APIs is April 29, 2019 (Europe: Paris), April 29, 2019 (America: Los Angeles).
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 53 apps that have signaled that they are ready for the deprecation, 5 that have signaled they are blocked, and ~650 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.
Recently closed issues
No new issues closed this week.
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 has not started 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 webhooks missing accountId and account type - This topic was reopened. I apologize for the miscommunication from last week. The Jira team is currently working on adding both accountID and account type to webhooks. See ACJIRA-1674.
Jira post function /triggered calls missing accountID and account type - This issue was split from the above. The Jira team has not started on this work yet nor provided estimates. See ACJIRA-1722.
Jira incoming webhooks missing accountId - Same as above. See ACJIRA-1692.
Jira does not recognize issue entity property aliases - The Jira team is currently working on this issue and expected it to ship this week. Unfortunately, the work is still in progress. We are getting new estimates for the ship date. See ACJIRA-1723.
Jira does not have an API to edit workflows - Same as above. 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 in 2 weeks. See ACJIRA-1710.
Email address hidden by default - Email address will no longer be provided to you through our product APIs for the majority of users. 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 on March 15, 2019 (Europe: Paris), March 15, 2019 (America: Los Angeles). See ACJIRA-1726
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 user references haven’t been migrated yet. We do not have estimates for how/when historical user references will be migrated. See ACJIRA-1715
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.