As you may know, Atlassian products represent users via an anonymous ID which is referenced in API calls in any context that has a user impact (e.g Pull Request reviewers, etc).
Although this solution is excellent from a privacy and compliance perspective, it can create challenges when needing to reconcile user information from external systems (like an identity provider) which usually use something like an email address as their unique identifier, and will not have any reference to the Atlassian generated user ID.
This creates a disconnect within automations and integrations which makes it often difficult to execute actions that reference specific users, unless your automation/integration already knows the Atlassian user ID required.
To address this, we recently made changes to the "List users in a workspace" API in Bitbucket Cloud, allowing you to filter the results from that API call down to specific users, based on an email address passed to the request as a query parameter.
This means you can now easily find the associated Atlassian user ID for a given email address, significantly reducing the friction involved in building automations/integrations that need to talk to other systems that use email addresses as their canonical ID for a user.
3 comments