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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How can you tell which automation rule(s) have run against a particular story?

We have what I consider to be a large number of automation rules in our Jira instance, and I'm seeing the results of some automation in some of our stories... primarily labels being written to subtasks.  I can't seem to identify which automation rule is responsible for the actions being taken.  Looking in the history of the stories in question, all I see is a message stating "Automation for Jira updated the Labels 3 days ago".

Digging through the automation logs has so far not revealed which automation rule is responsible; I may have not yet been successful searching for the right item... I am looking to see if there's a simpler way to ascertain which automation rule has updated a particular issue... are there any shortcuts into this, or am I solely left to searching the automation logs?

1 answer

1 accepted

2 votes
Answer accepted
Mark Segall Community Leader Feb 07, 2022

Hi @Randy O_Neal - Absolutely this is possible.  In the issues detail, you should be able to see a field called Automations with a clickable link Rule Executions that will give you a history of all rules that have executed against the issue:


Thanks... this is exactly what I was looking for, and it fills in the puzzle!

Hi @Mark Segall 

For my Jira Cloud instance, that feature only shows the last 8 rule executions run against an issue.  Are you seeing something different?


Like Randy O_Neal likes this


   It seems I'm seeing the same limitation... the last 8 automations are what I'm seeing.  I'll admit I am rather new to automations; I've known about them and studied them "on paper" for a while, but I don't have a lot of practical, hands-on experience with them.  It would seem like there would be a comprehensive log on this somewhere, though I suppose a poorly written automation could potentially fill up a dozen logs quickly.

Mark Segall Community Leader Feb 08, 2022

I don't see any formal documentation on this behavior, but yes appears to be the case. 

Note - You can see up to 90 days from the rule's main audit log if you wanted older, but you'd have to do a bit of investigation to find specific issue activity by cross-referencing the issue history with a matching rule execution time. 

Like Randy O_Neal likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events