nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Randy O'Neal

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?

Accepted answers

Mark Segall

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:

All comments

Mark Segall

Randy O'Neal

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

Bill Sheboy

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?

Thanks,
Bill

Randy O'Neal

Bill,

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.