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 last week’s post.
Recently closed issues
- To clarify the deprecation of AP.get.userTZ() this will not include un-deprecating timezone and locale in Context Parameters because the data is passed by URL. We are requiring apps to make an explicit request for this personal data should they need it.
- To clarify migrations with atlassian-connect-express (“ACE”), theres a new method available for user impersonation, asUserByAccountId() , which will work with accountIDs instead of user keys. If necessary, apps may use the new migration endpoints to convert stored user keys to accountIDs first and then use the asUserByAccountId() method.
Items in progress
Jira and Confluence webhooks bodies that contain username and/or user key missing accountID - We are working to update webhooks to contain both legacy user references, accountID and account type. Last week we communicated that this work was expected to be complete at the end of next week, however our dates have slipped and our current estimate is 28 Feb 2019.
Issues with updating data stored in product - As mentioned in last week’s post, Jira has already released a new endpoint which will be unaffected by the 29 Mar 2019 deprecation (see: /rest/api/3/bulk/migration). Confluence expects to release a similar endpoint in two weeks time.
Conversion of stored CQL containing legacy user references to accountID - The Confluence team is aware that this is an issue. They may be considering developing a similar solution to the PD Cleaner provided by Jira. We will provide more details next week on the status.
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.
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 will provide more detail next week.
Regarding the issue with the Jira PD Cleaner recognizing issue entity property aliases, the Jira team has committed to working on this issue. We don’t have a confirmed date yet but will provide an update on status next week.
Regarding the issue with ACJIRA-1625, we are currently looking into the status of that issue and will provide more detail within the 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.
If you are no longer blocked please opt in to the new APIs using the opt in mechanisms described in the migration guides to signal to us that you’re ready.