You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Welcome on Community!
The easiest way I've found to find my accountId is to click on my icon on the sidebar and then on the "Profile" link. In the URL you can find your accountId after the last "/" :
The bold part of the URL is my accountID :)
A programmatically available option is to use the REST api to search for a user and get his/her accountId in the JSON payload sent back.
Hope this helps!
Here is the REST documentation: https://developer.atlassian.com/cloud/jira/platform/rest/v3/
If you know the user name, email or key you can use the User endpoint, if not I would recommend to find members of jira-users group with GET /rest/api/3/group/member which includes the accountId as an attribute in its response payload.
Hope it helps!
Can you please tell me why I'm getting my account ID on a different format?
I'm getting it like this: atlassian.net/people/557058:db4467a5-32f3-48f9-be3b-687a1bc0468c
I need my ID on the format you showed us here for an API use and only get it like that above.
Can you help me?
Thanks a lot.
The Account Id not being listed inside Create and manage API tokens (or anywhere) is just plain stupid. If I am generating an API token, there is a 100% chance I will be using my Account Id with it. Why not provide it?
Same with custom fields. Just give me the id.
Having an official, recommended solution of "hover over this link and grab it from the URL" is abhorrent.
We have to change all our username references in JMWE and need to use the full string for Account ID. Some of our people have the short form (without the hyphens and 557058:) and some people have this longer form (with the hyphens and 557058:). I'm not sure why there are different formats but I think you do need the full string in the reference.
accountIds can take different formats, depending on when they were initially created by Atlassian, whether the user is (or was) a Jira Service Desk "portal-only" user, etc. Don't pay attention to the format.
In JMWE, you can easily get the accountId of any user by using the "Lookup user..." button in the toolbar of every Nunjucks editor on any post-function configuration page, as well as on the Nunjucks Tester page. Also, please note that accountIds in JMWE need to be prefixed with "accountId:" (which the Lookup user functionality will do automatically).
Seconding what David said - accountids can have a colon or not, be slightly different lengths, etc depending on various factors that there's no need to worry about.
Use the whole account ID either way.
Source: at one point I worked on the Atlassian account systems (but not anymore!)