Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

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

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.Epic Rule Automation.JPG

1 answer

1 accepted

0 votes
Answer accepted
Robert Wen_ReleaseTEAM_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 23, 2023

Hello @Darren Simons 

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

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.Epic Rule Automation Audit Log.JPG

Thanks!

Robert Wen_ReleaseTEAM_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 23, 2023

@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

Like Trudy Claspill likes this

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.

Suggest an answer

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

Atlassian Community Events