Edit issue error during Automation with error never seen before

[Eric Bergeron]

Recently started getting an error in our Automation audit logs while Editing an issue, for which I cannot see how to resolve. 

My system preferences are in English, but funny enough the error message comes out in french. I will therefore translate it myself for you below. 



Translated: "To ignore user notification, administrator or project administrator authorizations are required".

Here is the Edit issue action: 



Any ideas?

[Robert DaSilva]

Hi @Eric Bergeron , I haven't seen that error message before. However, it seems to indicate that the Rule Actor, the user that the automation system is using to take action, does not have appropriate permissions in the project.

On the Rule Details page, could you check what user is set for the Rule Actor? In most situations, this should default to "Automation for Jira". I wonder if this has been changed for your rule?

[Eric Bergeron]

Thank you for having taken the time to respond to my question. 

This is a new behavior, as the Actor has not changed. It's not "Automation for Jira" no, because some of our automations adding comments we want to be professionnal and be seen to our clients as though they were from our organization. We have therefore created a generic user for this. We don't want it to have Administrative rights.

Why would we want to be spammed with notification emails for every fripping automation anyway? 

I understand that this is by-design (as of now it seems), and that only way to resolved is to elevate our generic user's permissions. TY

[Robert DaSilva]

Hey @Eric Bergeron , thanks for adding context.

If you're not using the "Automation for Jira" user, I would ensure that the user you have as the Rule Actor has the appropriate permissions. As it sounds like you're changing this user on a per-rule basis, I would encourage you to double check other rules to ensure consistency.

I completely understand using a more personalized user, frequently I find myself using the "Triggering User" option for certain rules, depending on the specific need. It is very valuable to streamline some actions, and have them display as the same user causing them to occur.

Best of luck, sounds like you're already on the right pathway.

Robert

[Eric Bergeron]

Thank you for your response!

"Triggering User" (replaced by the user who triggered the event) would however most likely remove clarity in the Activity logs, wouldn't it? Making it hard to seperate actual manual actions of a user from the automated ones. At least, that's what comes to mind on my end. 

Un-related to this issue : I love that they've added rule validation on automations! 

Thanks again Robert, 
Cheers, 
Eric

[Robert DaSilva]

@Eric Bergeron You're right, if the rule author is the triggering user, I don't believe there is any indication the actions were taken as the result of automation.

This has benefits for certain scenarios, such as if automation determines the values of specific fields based on certain conditions. However it's not perfect for all scenarios.