-
Bug
-
Resolution: Unresolved
-
Medium
-
18
-
Severity 3 - Minor
-
10
-
Issue Summary
Projects migrated from external systems like Monday.com or Asana to Jira Team-Managed project using import to Jira(X2C) function 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: EDIT_ISSUES (Projects <project Id>)
Steps to Reproduce
- Migrate a project from Monday to Jira as a Team-Managed proejct
- Make sure the project access for the migrated project is set to Private or Limited
- Go to Project Settings > Automation and try to create rule with a simple issue create trigger and an Edit issue action.
- Action Edit issue > Error EDIT_ISSUES
- Make sure the actor remains "Automation for Jira".
- 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: EDIT_ISSUES (Projects <project Id>)
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.
- is cloned from
-
JRACLOUD-82460 Team-Managed project migrated via Cloud-to-Cloud migration fails to create automation rule with actor Automation for Jira
-
- Closed
-
- is related to
-
AUTO-442 Automation Rule fails with permission error in Team-managed project for Issue Types with Restriction applied
-
- Closed
-
-
AUTO-401 Team Managed Projects: When an issue on Next-Gen (TMP) has group restrictions, automation fails to execute for lacking permissions for the Actor
-
- Long Term Backlog
-