Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Automation rule to set Approvers

I would like to use automation to population the multi-users picker field, Approvers, for a JSM request.  The approvers can be any team members from the selected team (Object in Asset).  Here's what I've done:

  1. Use lookup object to search for the team - this is validated to be working correctly
  2.  In the Edit Issue action, I use the below advance options to set the value:  {
    "fields": {
    "Approvers": {{lookupObjects.Members.flatten.asJsonObjectArray("id")}}
  3. The above is returning this value:  Approvers: [{ "id": "1751" },{ "id": "1421" }]
  4. I am getting the following error in the rule audit log: THD-3378 (Pick another user as the selected user doesn’t exist. (customfield_13807))
  5. I have verify that the two users returned, 1751 and 1421, can be manually selected in the Approvers custom field

Any thought on why I am getting the error?

1 answer

1 accepted

1 vote
Answer accepted

Hi @WB 

The user id on Asset, does not match with the JIRA user account ID. 

You will need a field in asset to store the user as user picker - then you may get the correct id for that user. 

Approvers field will accept only JIRA User ID - not the object ID. So you need to convert somehow

Ah, that makes sense.  Thanks!

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events