Show name of automation in issue history

[Jochen Betz]

If a automation changes values in a issue, there is a log entry in the tab "history". Unfortunately it does not mention WHICH automation did this change.
Is there a way to show the name of the automation and what triggered it maybe even which user?

For example:

[Jochen Betz · Accepted solution]

So, referring to my own answer:

https://community.atlassian.com/t5/Jira-questions/Re-Re-Show-name-of-automation-in-issue-history/qaq-p/2876296/comment-id/1069716#M1069716

That does not tell you who did which change, but at least you have a list of automations which acted on the issue.

[Marc - Devoteam]

Hi @Rudy Holtkamp 

Each issue has an automation section in the issue details section on the right.

In this section you can use the refresh option to see the last 5 automation rules that have been activated on actions in the current issue.

[Rudy Holtkamp]

Yeah, but that does not always show the automation that caused the change.
I've an instance where a lot of automation will run when an issue has been created. A lot of them don't perform an action, but they are still visible in the section you mentioned. While the action that caused the change does not (always) show up (because it isn't part of the last 5 automations that ran).

[Marc - Devoteam]

Hi @Rudy Holtkamp 

You could add an add comment option in each automation rule with the smart value {{rule:name}}.

This would provide a comment on the issue which rule has been ran at the moment in time.

[Serhii Kibitkin_SAASJet_]

I'm afraid I've misunderstood your question, so I removed my post. Thanks for the comment.

[Rudy Holtkamp]

@Serhii Kibitkin_SAASJet_ how does your answer link to an automation rule?

[Rudy Holtkamp]

hi @Jochen Betz ,

Unfortunately there isn't. I've requested it several times at the Automation team, to add a link to the audit log of the rule that makes a change.

The only thing that you can do yourself, is note the time and go to the automation audit log and search the specific time. You might find more than one audit logs, but it will narrow it down.

[Jochen Betz]

Thank you @Rudy Holtkamp , that's a real pity. It makes work and debugging of issues so much harder.

I tried to check the global audit log, but in there I don't see any automation rule info. Checking all the audit logs of all automations.... is simply impossible.

So in short: We have a situation where changes are made in the system which we cannot find out who/why (with reasonable effort).

[Jochen Betz]

Correction to my previous statement:

There IS in fact yet another "log" I have missed so far. On the issue itself, to the right of the history there is a box with called "Automation". I have the feeling you need to manually refresh it, but after that, it's at least visible which automations have been acting on that particular issue.