Automation rule Failing field condition despite correct values

[Sayeda Abdelrazik]

Hi everyone,

I'm trying to create an automation rule that assigns story points to tasks based on a custom field value. However, the rule keeps failing at the field condition check, even though I can see that the correct values are set in the issue.

Context:

• We have a separate automation that creates an Epic, which then generates tasks and subtasks, copying values from the Epic to its children, including fields like the custom fields set as condition in this rule I'm having issues with

• Since this automation can take a few seconds, I suspected a timing issue but adding a delay didn't help.

• A general note that this rule was at some point working and stopped about a month ago and I have since tried to fix it (see below).
• "Check to allow other rule actions to trigger this rule. [..]" is enabled.

Issue:

• My automation runs but fails at the field condition step, saying that custom field value does not match the expected value, even though I can see it in the issue.

Things I Have Tried:

✅ Added a delay (to allow time for the other automation to populate fields).
✅ Changed field condition from "equals" to "is one of" (to be more flexible).
✅ Added a "Re-fetch Issue Data" action (to ensure the latest field values are checked).

Any ideas on what could be causing this?

Screenshot below of how the original rule looks like:

Audit logs

If I run the rule as above, the logs say that no actions were performed:

When selecting the field that did not match, it takes me to "Issue Type equals Task"

[Manoj Gangwar · Accepted solution]

Hi @Sayeda Abdelrazik, Please share a screenshot of the automation rule audit logs.
Also, confirm whether the field has been added to the edit screen or not.

Last thing, in the automation rule, please check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule.

[Sayeda Abdelrazik]

Hi @Manoj Gangwar 

Thank you for your help! I've now added a screenshot of the log in my post.

Could you clarify what you mean by "confirm whether the field has been added to the edit screen or not."? Thank you!

Yes, i do have that enabled.

[Manoj Gangwar]

I just want to confirm if the Story Points have been added to the issue edit screen.

Also, add a delay of 20 sec before re-fetch and then try.

[Manoj Gangwar]

As per the automation logs, the first condition is not met. So check if you have selected the correct Task

[Sayeda Abdelrazik]

Thank you, I added both the delay and the re-fetch issue action and it worked :)

[Bill Sheboy]

Hi @Sayeda Abdelrazik -- Welcome to the Atlassian Community!

From your question, I assume the rule you show has enabled the option in the details to "Check to allow other rule actions to trigger this rule..."  This would allow the first rule creating the issues (the one not shown) to trigger this second rule.

You describe adding the Re-fetch Issue action, and do not describe where you tried that...and your current rule image does not show this action.

The Issue Created trigger can fire so quickly that some issue data may not be available when the rule starts.  (i.e., a racetrack error)  This symptom can lead to failed conditions, errors, and other strange rule behavior.  When using the Issue Created trigger, I recommend always adding the Re-fetch Issue action immediately after that trigger.  This will slow the rule a bit, reloading the data before proceeding.

Please add that action and re-test your rules.

Kind regards,
Bill

[Sayeda Abdelrazik]

Hi @Bill Sheboy 

Thank you for your help! Yes, that option is indeed enabled.

I had a few versions of this rule, so only included the initial one that used to work. I had the re-fetch action set right after the trigger and it still didn't work. I had also tried re-fetching after one of the conditions with no success.

[Bill Sheboy]

Please re-add that action after the trigger to ensure some level of rule predictability.  You appear to be using Jira Cloud, and so there is always some variability to performance.  Including the Re-fetch Issue action after this trigger reduces the chance of errors / problems.  

Also note: the Delay action has no impact for this scenario as that only pauses rule processing and does not reload the data before continuing.

Based on the audit log entry you just posted, the rule triggered for issue LOCP-42272, and the first condition on issue type did not pass.  What is the issue type for that one?

And as the rule triggered 6 times in under 10 seconds, I recommend expanding all 6 of those log entries to understand which conditions did not pass and if those were expected.

[Sayeda Abdelrazik]

I will re-add the re-fetch action after the trigger - thank you!

There's another rule that generates tasks once an epic with certain conditions is created. 8 issues didn't failed in this rule (screenshot in my post), one being the epic, which makes sense. However, the 5 created tasks are incorrectly failing the same condition: "Issue Type equals Task"

[Mikael Sandberg]

Hi @Sayeda Abdelrazik,

Welcome to Atlassian Community!

If you include the Audit log showing the error that would help to answer questions like this.

Your timing suspicion is probably right. You can work around that by either adding a delay in your automation that sets the story point, or from the automation that creates the task use a send web request at the end, and then change the above automation to trigger on incoming webhook. That way you can control when the above automation triggers.  

[Sayeda Abdelrazik]

Hi @Mikael Sandberg

Thank you for your help here! I have now added a screenshot of the log in my post. I did add a delay after the trigger in the rule in one of the versions I created but it still failed to work as expected. I don't have extensive rights in Jira to be able to set webhooks, so I would need help from the IT team in my company.

[Mikael Sandberg]

If you can create automations you can create webhooks, they live within the automation rule, it is not set up on the admin side.

[Sayeda Abdelrazik]

oh my bad! Had no clue, never really had to go that far - I will try this out and see if it works :)