Global Automation running incorrectly on issue types and giving "No Actions Performed"

[Darren Simons]

I have a Global Automation set up to run as shown in the attached screenshot. The issue I am having is that the rule runs on issue types = Stories in addition to Epics even though I have it only set to run on issue type = Epic. This is counting heavily against our allotted rule automation limit even though it is running as "No Actions Performed" each time it runs on a story. Seeing as this is set to only run on Epics this would be a very small subset of issues if ran correctly but it is not working as intended.

[Robert Wen_ReleaseTEAM_ · Accepted solution]

Hello @Darren Simons 

Do you have output from Audit Logs?  It may shed some light on what's going on.

[Darren Simons]

Below is an example of what I see each time this happens. The issue (DLIQ-3468) is a story and not an epic so I don't understand why that is triggering the rule automation considering how it is set up from my above question.

Thanks!

[Robert Wen_ReleaseTEAM_]

@Darren Simons , the reason the automation is running is because of the trigger.  Since this is a global automation, the update of ANY issue on ANY project will start the execution of the automation.

After evaluating the condition, any stories (because they aren't Epics) fall out and no action is performed against them.

In the current charging model, if a global automation is triggered, it counts as an execution.  That changes November 1, where if actions are performed on a global automation, you get charged for that.

New charging rules are here: https://www.atlassian.com/blog/announcements/cloud-automation-packaging-update

[Darren Simons]

Ok thank you for your help investigating! I will not worry about the No Actions Performed ones moving forward as those will not count towards our monthly totals.