Note: The root cause for this was fixed on December 1st 2023 in this PR. Projects migrated before then are still affected, but projects migrated after December 1st 2023 should not be affected. 

Issue Summary

Team-Managed project with Private Access Type migrated via Cloud-to-Cloud migration fails to create Automation rule with actor Automation for Jira.

Error is thrown when creating rule:

Error   

The rule actor for this rule is missing some required permissions:  BROWSE_PROJECTS (Projects 10011) TRANSITION_ISSUES (Projects 10011

Steps to Reproduce

1. On instance A have a Team-Managed project
2. Migrate this TMP to instance B via Cloud-to-Cloud migration
3. Make sure the project access for the migrated project is set to Private or Limited
4. Go to Project Settings > Automation and try to create rule from template, e.g. "When all sub-tasks are done → move parent to done"
   1. Action transition issue > Error TRANSITION_ISSUES
   2. Condition with JQL > Error BROWSE_PROJECTS
5. Make sure the actor remains "Automation for Jira".
6. Error will be thrown.

Expected Results

The rule is created successfully

Actual Results

The rule fails to create with error:

Error   
The rule actor for this rule is missing some required permissions:  BROWSE_PROJECTS (Projects 10011) TRANSITION_ISSUES (Projects 10011)  

Workaround

• Change the actor of Automation rule from "Automation for Jira" to either some user or "User who triggered the event". In this case the action will be performed by particular user rather than "Automation for Jira" user.
• Change project access from Private to Open. In this case any user who can access to your Jira site will be able to browse the project.