I would like to assign the "User who triggered" actor to an automation rule with a manual trigger.
A user has created some rules which have a manuel trigger however when the rules are run, the history shows the actions were done by user who created the rule (the original actor). For auditing purposes, this is not ideal. The desired outcome is for the issue's history to reflect the user who ran the rule, as opposed the owner of the rule. I also, for the same reason, do not wish to grant them the impersonation permission.
I experimented by creating a rule as a jira administrator to see if it would make a difference, I also granted the impersonation permission before re-creating the rule, however in al those instances I never had the ability to set the "user who triggered" actor, at best i can pick a specific user but I cannot make it dynamic so that the user who runs the rule becomes the user who is seen doing the action in the issue's history.
Any guidance would be appreciated. Thank you.
Hi @Erik Godin ,
Unlike Cloud, Jira Data Center does not currently provide the option to set the rule actor to "User who triggered the rule" in the rule details. This is a known limitation, and there is an open feature request for it - https://jira.atlassian.com/browse/JIRAAUTOSERVER-254
As a workaround, if you'd like to identify the user who triggered the automation, you can add a Log Action to the rule and use the following smart values:
{{initiator}}
or
Triggered by: {{initiator.displayName}}
This will log the name of the user who initiated the rule in the automation audit log.
Hi @Yashaswini YK ,
I'm looking at your screenshot and it looks like Jira Cloud. This assumption is backed by the wording "Space" in your screenshot, as well as based on the options I see under the menu you opened, i.e.: Connections, which isn't available on my Jira software DC instance.
Can you please confirm whether the screenshot you shared is from Jira Cloud or Jira Software DC?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Erik Godin ,
I realized my previous response included screenshots from the Cloud version. I've now updated the original answer to reflect the correct behavior in Jira Data Center.
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.