Forums

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

Jira automation reads only one value of multi-select field

paulius.janulevicius January 9, 2024

Hello guys
I'm setting automation rule that brings the status of the issue back to the previous one if condition doesn't match

I am using smart values condition, and I am trying this in a second value comparison: {{customfield.accountid}}

But for some reason, it works only with a single user in that field. If there is a second user added - it doesn't work.

Any ideas?

1 answer

1 vote
Jack Brickey
Community Champion
January 9, 2024

Hi @paulius.janulevicius ,

would you mind sharing a screenshot of your full automation rule?

paulius.janulevicius January 9, 2024

Screenshot 2024-01-09 at 17.14.10.png

paulius.janulevicius January 9, 2024

Thanks for helping! 

paulius.janulevicius January 9, 2024

CAB is a custom field
If that field contains more than two users, Jira recognizes only the first user added to that field.

Jack Brickey
Community Champion
January 9, 2024

Hi @paulius.janulevicius , so I believe the issue is related to the fact that a multi select field is a list of values. I found this post where @Bill Sheboy explains this by example. You need to iterate over the list to check for each possible selection. Bill, may be able to provide more detail here.

paulius.janulevicius January 9, 2024

Thanks!
I've just reviewed the post and tried to use a list of values

Now the log returns several account IDs, but the rule still doesn't work...

It still reads only one user in that custom field... 

paulius.janulevicius January 9, 2024

Screenshot 2024-01-09 at 21.29.14.png

paulius.janulevicius January 9, 2024

Even logs show that the initiator account ID is there, but the rule still brings the status back to the previous one... 

any more ideas folks?

Bill Sheboy
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 Leaders.
January 9, 2024

Hi @paulius.janulevicius 

Adding to Jack's suggestions...

Are the values in the condition reversed; don't you want to check if the initiator's account ID value is not present in the list of possible values?

As shown, that condition would test if the initiator does not contain the entire list.

Kind regards,
Bill

paulius.janulevicius January 9, 2024

Omg I'm so sorry guys for bothering you because of my brain fart...
It works now!
Anyway, many thanks for suggesting to take a look at Bill's example, it helped me a lot to get closer to the final outcome!

And thanks for pointing out my logical mistake!

Like # people like this
Jack Brickey
Community Champion
January 9, 2024

Hi @paulius.janulevicius , it would be great if you would post your final rule here as it will most certainly help future folks.

Like Aaron Lane likes this

Suggest an answer

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

Atlassian Community Events