Reference automation rule name in Jira Software automation

[Inna S]

Hi, 

With numerous automation rules and workflow automation, I'm now looking for the way to 'sign' the changes made to the issues by the ID or name of the automation rule that made the change to the issue.

Till now I've been doing this manually by adding an extra step of 'comment' to edits made by automation rules. But this is a matter of discipline and thus is not reliable.

I also do not see a metadata or smart value that would contain the rule ID.

I see similar question on JSM, with no solution.

Any suggestion?

Thank you.

[Bill Sheboy · Accepted solution]

Hi @Inna S 

The smart value for the rule's name while it is running is {{rule.name}}

Without seeing the specifics of your scenario, I can anticipate using this smart value, as you describe, will both increase the length of rules and may be brittle for maintenance.  (Brittle, because I do not know if this is a supported smart value or just "found" by the community.)

Kind regards,
Bill

[Inna S]

Thank you, @Bill Sheboy . This is the one I was looking for.

Do not care about 'brittle' because all of Jira 'features' are so much unstable this would be a negligible detail.

[Bill Sheboy]

I withdraw my brittle observation as Atlassian just added this smart value to the docs in the last few days!

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--rule--

[Michel Neeser]

Hi @Inna S

On every issue, there is a section "Automation" in the sidebar showing the automation rule executions which affected the current issue:

By clicking on the rule name, you will be redirected to the detail page of the rule where you can access the audit log. If you compare the timestamps, the audit log shows you exactly what happened in the rule execution.

Hope this helps.

[Inna S]

Hi @Michel Neeser , this is nice, but I need to see the rule name in the history record (not possible) or be able to use it in the comment upon change.

Rule audit log does not help as we have tens of rules executing on issues and sifting through would be a great waste of time.

[Maysarah Abu-Laban]

Thank you. Very helpful

[Sanjen Bariki]

Hi @Inna S ,

Could you please let me know the actual requriment in details to understand the query..?

With example will better to get the solution..

Regards,

Sanjen

[Inna S]

Hi @Sanjen Bariki , 

This is to overcome another Jira deficiency. 

We have tons of rules, automation and workflows, that all change issue fields. Most run as an undescriptive service user and leave no proper trace in the history. It is virtually impossible to find what rule made a change. So when the change is problematic, it takes a good memory of the system architect to recall what rule could this be and then sift through the rule log. Time consuming and not sustainable.