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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


Automation for Story being added to an Epic

Hello, in prep for the upcoming change to Jira Automation limits I've been reviewing the automation rules that are already in place. Most seem fine but I have one rule that fires on any issue update event within a given project. That seems extreme and likely to run me into trouble with the new limits so I'm hoping someone here will have a better idea for how to accomplish what this rule accomplishes.

Basically what the rule is seeking to accomplish is to have any story that gets added to an epic inherit the value of two custom fields on the epic. Specifically, there are custom fields called "Program" and "Time Classification". When a story is added to an Epic we want the story to inherit the Program and the Time Classification from the Epic.

I looked at the Issue Linked trigger but it does not appear to fire when an epic is linked to a story. The only way I could find to do this was to trigger on Issue Updated and then look at the changeLog to see if the Epic link changed. Seems inefficient but it was the only way I could see to do it when the rule was written and since there was no limit on rule executions within a single project I decided it was fine. Now if I'm only going to get 1700 rule executions/month...that might be a problem.


1 answer

1 accepted

2 votes
Answer accepted
Trudy Claspill
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 24, 2023

Hello @Phil Beckman 

This rule will count towards your executions only if the Edit action is executed. A rule is not counted as an execution every time it is triggered. As per the documentation:

1. Only rules that perform a successful action will count towards the limit

In today’s model, rule runs count toward your usage limit, even if they perform no actions. For example, let’s say you have the following rule set up:

  • Trigger: When an issue is created

  • Condition: If issue type = Bug

  • Action: Set Affects version field to Last released version

This rule would trigger and count toward your execution limit every time an issue was created, even for issues that aren’t bugs. In the new model, the rule will only count if the issue created is a Bug and the Affects version field is successfully updated.

OH! How did I miss that?

In the words of SNL's Gilda Radner....nevermind :)

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.
Oct 24, 2023

Hi @Phil Beckman 

Yes, and to Trudy's answer...

That change to the packaging model describes which actions count and do not count for the new limits...And conditions do not count (as of the time I am posting this :^)

Thus you could reduce your usage count by adding conditions to test if Program and Time Classification have changed (due to the new parent) and so only proceed with the Edit Issue in that case.

Kind regards,

Like Trudy Claspill likes this

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events