-
Bug
-
Resolution: Duplicate
-
Low
-
Severity 3 - Minor
Issue Summary
When trying to run an automation rule in a Team-managed Project for issues having restriction applied, it gives an error stating "Actor does not have permission to view one or more issues, or the issue was deleted (please check permissions and issue security levels)", in spite of the fact that actor is part of the restricted role.
Steps to Reproduce
- Create an Automation Rule
- Set the restriction for an issue type
3. Execute the Automation rule for the same issue type with the actor part of the restricted role.
Expected Results
The rule should successfully run.
Actual Results
Automation rule fails with the permission error:
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
- relates to
-
JRACLOUD-83386 Projects migrated from External tools to Jira Team-Managed project using import to Jira function fails to create automation rule with actor Automation for Jira
-
- Gathering Impact
-
-
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
-
- links to
- mentioned in
-
Page Loading...