why is the status of the automation says 'no actions performed' while it actually worked?

Yousif Al Rawahi April 3, 2024

I have created an automation when an issue is created, it will automatically create 6 subtasks, this works perfectly. But then I have created another automation, when the issue is created, and if certain conditions are met (as shown below), it will attach a form to a specific subtask. When I checked, it actually worked, but when I checked the audit log, it says 'no actions performed'. And it's checking on a wrong subtask (which is 'SCRM-134'), while it should check on 'SCRUM-129'. What could be the problem here?

 

Screenshot 2024-04-03 120546.png

 

 

Screenshot 2024-04-03 120529.png

 

Screenshot 2024-04-03 120509.png

2 answers

1 accepted

1 vote
Answer accepted
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.
April 3, 2024

Hi @Yousif Al Rawahi 

From what you describe, you have two automation rules, and the actions of one (create the subtask) will trigger the other (to attach the form).  This second rule has probably enabled the option "Allow Rule Trigger".

The Issue Created trigger can fire so quickly that some issue data may not yet be available to the rule.  This will appear as symptoms like rule errors, missed conditions, or other unexpected behaviors.  As you are using two rules chained in sequence, I hypothesize this effect is more likely to occur.

The fix / work-around is to always add the Re-fetch Issue action immediately after the Issue Created trigger.  This will slow the rule down a bit, reloading the data before the rule steps proceed.  Please try adding that action to your second rule and re-test.

Kind regards,
Bill

0 votes
Rilwan Ahmed
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 3, 2024

Hi @Yousif Al Rawahi ,

Instead of 2 conditions, can you try using "JQL condition"

Example JQL: type = Sub-task and summary ~ "Line Manager Tasks"

image.png

Yousif Al Rawahi April 3, 2024

I have tried this using JQL condition, it still doesn't work

Rilwan Ahmed
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 3, 2024

Hi @Yousif Al Rawahi 

The reason could be that the second rule is starting before first is completed. 
Can you share me the first rule. I will try for a workaround. 

Meantime, you can try branching

image.png

More details: https://support.atlassian.com/cloud-automation/docs/jira-automation-branches/#Related-issues

Suggest an answer

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

Atlassian Community Events