Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Extract the reviewer name and use that name in assignee field.

Tasneem Talawala
July 22, 2026

When a ticket is created, the assignee field is Unassigned. What I am trying to achieve is to extract the reviewer name from the requirement fields. Use that name in the Assignee field

The requirement field in the ticket looks like this:

Link: xxx.com (SharePoint link)
Reviewer: {"ABC":"ABC"} (The names extracted from SharePoint)
Owner: ABC (The names extracted from SharePoint)

The reviewer can contain more than one name. The first name goes to Assignee field and remaining goes to collaborator, if it is doable.

I created the flow, and I tried  a lot of things, but nothing seems to be working. My current flow is :

Trigger: Work item created

Action:
Created Variable

Variable name
Access using {{reviewerRegex}}. 
Smart value
Reviewer:\s*\{\s*"([^"]+)"
Action:
Assign the work item
Assign the work item to
Smart value
User
{{jiraUser(issue.description.match(reviewerRegex)).accountId}}

Can anyone please help me correct logic and condition?

1 answer

0 votes
Gor Greyan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
July 22, 2026

Hi @Tasneem Talawala

Could you clarify what the reviewer field is?

Is it a plain text field containing the reviewer's name?
A user picker field?

Tasneem Talawala
July 22, 2026

Reviewer is not field. Reviewer is plain text the reason the names are in this format is {"ABC":"ABC"} because there is Power Automate flow which is set for creating review ticket for document on SharePoint which are due for review. The reviewer name is extracted from there.

Reviewer is inside the requirements field.

If that makes sense.

 

Gor Greyan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
July 22, 2026

@Tasneem Talawala

Thanks, that makes sense.

Since the reviewer is stored as plain text inside the Requirements field, you can extract the name using Automation, but the extracted display name cannot be used directly as an Assignee reliably. Jira Cloud needs the user’s Atlassian account ID.

The most reliable solution would be to update the Power Automate flow so that it sends either the reviewer’s email address or, preferably, the Atlassian account ID

If changing the Power Automate flow isn't possible, you can extract the reviewer name from the Requirements field and then use a Send web request action to search for that Jira user through the REST API. The response will contain the account ID, which can then be used in the Assign work item action. Atlassian documents a similar approach for extracting a user value from text, searching for the user through the API, and updating a user field.

https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-user-search/#api-rest-api-3-user-search-get

Tasneem Talawala
July 22, 2026

I tried using API but the body:empty which means the search didn't return any results

Gor Greyan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
July 23, 2026

@Tasneem Talawala

The query parameter needs to contain a value that Jira can match against a user's profile, their display name, or email address. If the value extracted from the Requirements field doesn't exactly match a user, the API can legitimately return an empty result.

Could you please share.

- Value you're extracting from the Requirements field,

- Request URL/body you're sending to the user search endpoint (masking any sensitive information)

- Response status code?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events