How to assign the action of an automation rule result to a user rather than the automation owner

[Miguel Rodriguez]

I created some automation rules that inherit some fields and labels from parent tickets when the new child is created. However in the History it appears as if I did the change of fields. Is there an option to make the history appear under the name of the person who is creating the new child issue or a "system" change, rather than my name?  

[Trudy Claspill · Accepted solution]

Hello @Miguel Rodriguez 

How does the rule get triggered? Is it triggered by an action that is executed by the person who creates the child issue? 

If so, and if that person has sufficient permissions themselves to do everything that is in the Automation Rule, then you can change the Actor of the Automation Rule (on the Rule Details page for the rule) to be "User who triggered the event". Then all actions taken by the rule will be attributed to the user whose actions triggered the rule.

Other options are to set it to Automation for Jira or to one of the specific individuals that it allows you to select.

[Miguel Rodriguez]

Thanks a lot @Trudy Claspill . The option of user who triggered the event seems ideal. My trigger is the creation of the child issue, so the user that is creating it, has all the rights. However, then I type it it does not come as a valid option and therefore I cannot save the changes. I am using Jira 9.4 Datacenter. Could it be an option only for cloud? OR maybe because I am just project admin and not site admin? 

Thanks. 
 

[Trudy Claspill]

I think it might be an option only for Jira Cloud, unfortunately.

This is the page that includes information about the rule actor for Data Center.

https://confluence.atlassian.com/automation/run-jira-automation-rules-as-another-user-1141480609.html

It sounds like perhaps you can only choose specific users rather than have have it set dynamically based on who triggered the rule. Unfortunately I don't have access to a Data Center instance where I can investigate.

You might want to consider creating a generic user account that could be set in the Rule Actor field so that you could tell that Automation was causing the changes vs. and individual person.

[Miguel Rodriguez]

Thanks  @Trudy Claspill , I think we have one with the name of the team of site admins and automation suffix that I can use. 
This info has been very helpful, 

Thanks again 

[Mark Segall · Accepted solution]

Hi @Miguel Rodriguez - The action will always perform the action as the Actor.  Jira Server does not default to it, but you should have the option to change it to Jira Automation Actor so that you can at least delineate what was user vs automation in the issue history.