Hi Atlassian community
Major API changes are arriving: https://developer.atlassian.com/cloud/jira/platform/api-changes-for-user-privacy-announcement/
And this will break our integrations between systems
Reason: We lookup users in JIRA based on AD account firstname.lastname
GET https://jira.atlassian.net/rest/api/2/user/search?username=firstname.lastname
But if username is deprecated on the APIs, how can we even get the unique identifier(AccountID) based on AD details?
As JIRA Admin my service account needs to be able to lookup JIRA users based on information I already have in my AD(SAML/UserID)
If this is not possible, I would have to MANUALLY maintain a mapping list between JIRA and my other systems = Waste of time every single time a new users gets onboarded!
As an Atlassian admin, it would be nice to have some kind of simple control of the mapping/lookup between JIRA and other systems based on simple existing information like firstname.surname or emailaddress.
So will there be any exceptions to JIRA(ex ADMIN account) on the API for service/integration account usage?
Thanks in advance
/Morten
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.