You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.
@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