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?
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!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is there a similar field available for Jira Data Center version aswell ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'd be interested in a feature/field like this for Data Center as well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.