I have created a simple Automation Rule that can be triggered manually. The rule changes the label and assignee field. I have set the Rule Actor as "User who triggered the event".
When I run the rule manually, my name is seen in the History tab as the user who changed the fields. When someone else runs the rule, their name is not shown in the history tab. Instead, the user shown is Automation for Jira.
All users who run this rule have the permissions to change he label and assignee fields. There is no permission issue. Then why doesn't their name appear in the History tab
I recreated the rule and ensured that the Actor was set to "User who triggered the event", before publishing the rule. That seems to have fixed it.
Even cloning the rule works. No need to recreate the rule from scratch.
Thanks to this post for the suggestion: Automation Rule Actor not Actor who triggered the event
@Manish Keswani what you have seems correct to me, so I'm not really sure.
One idea I have as a possible work around would be to add an automated comment that says something to the effect of "Label and assigned changed by " and then use a smartvalue for the initiator. So even though the comment will say "Automation for Jira" you can see who did it IN the comment.
I think the smartvalue is {{initiator}} (but not 100% on that).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your input. We have filters and JQL based on the user who updated or commented on ticket. Those filters and JQL will fail if the user is set as "Automation for Jira".
We also have a very large team. At a glance, every ticket will seem to be updated by the Automation user. Users will have to read each comment carefully to understand who actually posted the comment or made the change.
I am hoping someone can tell me which permissions are required for users so that their name appears in the History tab.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you just add a screenshot of the action. It would be interesting just to see what you have there too.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The Blue Actions are when I run the rule. The Red Actions are when someone else runs the rule.
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.
I recreated the rule and ensured that the Actor was set to "User who triggered the event", before publishing the rule. That seems to have fixed it.
Thanks to this post for the suggestion: https://community.atlassian.com/t5/Jira-Software-questions/Automation-Rule-Actor-not-Actor-who-triggered-the-event/qaq-p/2408794?utm_source=atlcomm&utm_medium=email&utm_campaign=immediate_general_reply&utm_content=topic
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Spend the day sharpening your skills in Atlassian Cloud Organization Admin or Jira Administration, then take the exam onsite. Already ready? Take one - or more - of 12 different certification exams while you’re in Anaheim at Team' 25.
Learn more
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.