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?
would you mind sharing a screenshot of your full automation rule?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
CAB is a custom field
If that field contains more than two users, Jira recognizes only the first user added to that field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @paulius.janulevicius , it would be great if you would post your final rule here as it will most certainly help future folks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.