Automation error regarding rule actor

[Collista Lewingdon]

Recently our company switched from team managed projects to company managed projects. After transitioning to the new project styles the automation rules were copied into the new project while being sure to include the new company requirements. For some reason the automation rules refuse to work in the new project and we have been getting a few errors. One of them says that the rule actor doesn't have permission to view the event that triggered this rule. 

Which does not make sense since the rule actor is Automation for Jira 

I have made sure that the project role (atlassian-addons-project access) has access to all permissions within the project. And it does.

Yesterday it was only one rule that was being affected and today it is all almost all the rules. 

[Bill Sheboy]

Hi @Collista Lewingdon 

The configuration of each Team-managed project (TMP) is distinct, although they might have also used some global fields shared by Company-managed projects (CMP).  And, automation rules store a bunch of id-specific information for issue types, fields, workflows, etc.

Without seeing the details of the rule(s) with this symptom...

What may have happened is when the rules were copied (or just changed in scope from the CMP to a TMP), one or more internal id values is "stuck" in the JSON.  One way to check that is pick a rule with this symptom and re-create it from scratch to test for the symptom.

Kind regards,
Bill

[Collista Lewingdon]

First of all, I made sure that all of the fields for the transition were correctly changed in the new project. No issues were transitioned. Only the rules. This particular automation rule was created from the ground up in the new project. 

Here are the details of it. 

Here is how the rule is structured. 

Yet this rule still had the error "The rule actor doesn't have permission to view the even that triggered this rule" Generally this error is associated with the project role (atlassian-addons-project access) not having access to something but as I clarified in my above post, it has access to all permissions within the project. As you can see from the first image I posted of the rule details, Automation for Jira is the actor. 

Here is a more in depth view of how the rule was created

[Bill Sheboy]

Thanks for those rule images.  Let's try the simplest thing which could be causing this symptom...

This rule uses the Issue Created trigger, and that has a known "racetrack error" where the trigger can fire so quickly some data may not yet be available for the rule.  This can lead to all types of weird errors and unexpected behavior (e.g., conditions do not match, permissions errors, etc.).

The fix for that is to always add the Re-fetch Issue action immediately after the Issue Created trigger.  This will slow down the rule a bit and reload the data before proceeding.  Please try adding that and re-test the rule.