Link Jira portal users to user assets

[Teke Máté]

Hi!

We have been using Jira Cloud for 2 years. We have portal only customers, with hundreds of tickets. Now, since we would like to implement an approval workflow that checks the user's manager, we added our users via entra ID to Jira Asset Management. My issue is that these user objects are not linked to the Jira Portal customers. I have tried to linked them with email or name, but it does not work via Entra migration. 

Now, I figured that the Jira User field requires a Jira User ID, but I can not find our jira portal users, and their IDs anywhere. What are your suggestions? 

The last option is to link them one by one, but obviously with hundreds of users, it is not very user friendly. I have tried to write autimations, with no success. Any suggestions?

[Marc -Devoteam-]

Hi @Teke Máté 

See this KB article; https://support.atlassian.com/jira/kb/match-users-in-csv-import-to-user-type-attribute-of-assets-objects/ 

This will provide what you need.

[Teke Máté]

Hi!

Thank you, I will try your method.

However, I made a user export, and while I thought that it is an export of our agents and paid users only, it contains the portal-only users as well, becuase when we connected our Jira system with entra (for SSO), it pulled everything.

[Arkadiusz Wroblewski]

Hello @Teke Máté 

You’re on the right track. The big thing to know is: Jira “user” fields don’t work with name/email. They work with the Atlassian accountId. Portal-only customers still have one, they’re just harder to “browse” in the UI.

So I wouldn’t try to manually hunt IDs. I’d do it like this:

Use the ticket itself as your source of truth. Every request already has the reporter, and you can read:
{{reporter.accountId}}

Then store that in Assets.

Practical approach that scales:

Add a simple text attribute to your Assets user object like Atlassian accountId.

Build an automation that, on issue created (or request created), finds the matching Assets user by email and writes {{reporter.accountId}} into that attribute.

For the old customers (hundreds of tickets), run a scheduled rule that processes older issues in batches and backfills the same mapping (so you don’t do it one-by-one).

Once Assets has accountId (and your manager relationship), you can set approvers / route approvals reliably, because now you’re dealing with the exact identifier Jira expects.

Have a great Day.