Automation worked, suddenly not working

[Blake]

I created a rule 14 days ago. simply to transition the ticket status to waiting for customer or support based on most recent commenter. This was working flawlessly for about 10 days. 

The last few days, I noticed it is not transitioning. neither "if" nor the "else if" condition is working. 

For reference, no agents have been added, no other rules have been implemented, no agent permissions have been changed, etc. I have simply been going about my work. I do see the warning message on the right of the screen, however that was there during creation of this rule. 

Any help is appreciated. 

[Trudy Claspill]

Hello @Blake 

Can you add a Log action step here:

The Rule Details say that the Actor of the Rule is the Initiator (the user who executed the action that triggered the rule).

The error message that you are getting implies that the user does not have permission to see the issue, so the steps in the rule cannot be executed.

After adding the Log action when the rule fails again take a look at the Audit Log to see what it notes about the Initiator of the rule. Is that person a JSM Agent?

[Blake]

The error message that you are getting implies that the user does not have permission to see the issue, so the steps in the rule cannot be executed.

Yes and this is without a doubt false (unless something changed somewhere, somehow, by someone) since I am our org admin and have been able to see issues, edit, as well as my other agents. we are all JSM agents and all can see issues, so this error is a direct contradiction of what is actually taking place. 

[Trudy Claspill]

Did you try adding the Log action as I recommended to confirm who the rule is seeing as the Initiator of the rule?

[Blake]

I did not. now the rule seems to trigger when i comment, but when customer comments, no change.

[Trudy Claspill]

I recommended you use the Log action to confirm who the rule is seeing as the Initiator of the rule.

Alternately, simply change the Actor of the rule to Automation for Jira.

I believe the problem is that you have the Actor set to Initiator, and the actions and conditions in your rule can only be executed by a user that has JSM Agent access to the project. Customers don't have that level of access, so when the rule is triggered by a customer comment, making the Customer the Initiator, the Initiator is a user that doesn't have the necessary permission to execute the condition checks and actions.

[Nicolas Grossi]

@Blake you might take a look ast this thread: https://community.atlassian.com/t5/Jira-Service-Management/Automation-failed-Error-Actor-does-not-have-permission-to-view/qaq-p/1816718

[Blake]

Thank you. However after reading this post, it does not resolve the root issue here. My comment just posted to that thread:

I am seeing that adding this access has fixed your issues. But I am confused; this is in fact not a true fix of the original problem..

OP says the problem is that suddenly automation has stopped working, with zero changes made. So, why would adding an "access" into roles fix this, if it worked for X amount of time without this at first? This proves that at one point, this "access" was not necessary.

[Nicolas Grossi]

@Blake Could you please paste the audit log of the rule ?

[Blake]

I am not sure how to paste the whole log, but i took a ss of one specifically that didnt trigger.