nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

The "Issue fields condition" in Automation rule does not work

Alla Austin

I need to assign the issue to a particular assignee when the issue is created and the "Request participants" field contains a specific email address.

I use simple

Then I test by sending the email request with "Name 1" in CC, the issue is created, the "Name 1" is in Request Participants:

but the Audit log reports that "The following issues did not match the condition:" and the rule is not applied.

It seems pretty straightforward, so I don't understand what can be the issue here. I tried using the Advanced rule with accountID, etc, and the result is the same.

Any help is much appreciated!

Accepted answers

Pramodh M

@Alla Austin

How about you include the fetch issue data and then add the users list in request participants and check once!

Thanks

Jack Brickey

Hi @Alla Austin , one suggestion I would make is to use the "log action" and log the Request Participants info. Do this just after trigger. Then when you test we can see what is in the field. I will try to do a quick test myself when I have a sec.

All comments

Pramodh M

@Alla Austin

How about you include the fetch issue data and then add the users list in request participants and check once!

Thanks

Jack Brickey

Hi @Pramodh M , i don't think this is a situation where fetch data would help. I used when you have an action upsetting some field within the automation rule and then you want to leverage that field value in the next component. So fetching the issue data reloads all of the data for that issue picking up the new change. But maybe I'm missing the point here.

Jack Brickey

Actually...it appears that the re-fetch may help but not yet sure why. I will explain in my test results.

Jack Brickey

so i did some testing using the below automation. Initially w/o the refetch actions.

Test 1: without the refetch the Assign wasn't happening because the Condition failed as @Alla Austin mentions. Note - looking at the test issue the RP did have the Cc user as well.

Test 2: Based on T1, I theorized that for some reason the RP field was not getting populated at create time before automation triggered. So, without refetch I changed the trigger to be on a Comment. The test was successful and issue assigned as expected.

Test 3: I decided to use the re-fetch data to see if it would address the apparent race-condition. As shown in my automation I added two re-fetch actions, though this is over-kill. The test was successful.

Summary: for some reason the RP data is not added before the automation triggers. I hope to learn why.

Alla Austin

Hi Jack,

Thank you so much! I did re-fetch (right after the trigger "case created"), and it worked. Last night I had a suspicion that for some reason, the PR field was populated after the case was created (even though it makes no sense), but I was so irritated it did not work that I gave up and created a cry for help on here

Thank you, @Jack Brickey and @Pramodh M, for responding so fast! I am not an experienced user of Automation and did not know about the re-fetch function. My rule works now. @Jack Brickey thank you for going the extra mile!

Pramodh M

Hi @Alla Austin

Can you please accept my answer as well!!

Crazy right @Jack Brickey ?

I think we should have a word with Atlassian team on this one

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

automation

jira-service-management-cloud

jira-service-management