Details
-
Suggestion
-
Resolution: Duplicate
-
0
-
Description
When applying an Automation rule to Jira for mulitple projects this set the rule as Global.
However only Jira Admins can update the Global rules.
It would be good if for any of the projects that are in scope for the rule, where a user is a project Administrator, that they have the option to update the rule.
e.g.
To set/remove any project's they administer in the rules scope,
To edit the triggers/conditions/actions for the rule (the rule audit capture who made the change and when).
the audit is visible to Jira Admins or any other "in scope" project admins for transparency of changes made.
This would enable, for example, where we have multiple JSM projects suing the same rules on each project, to be able to use a shared rule across those service desks. The project Admins can manage one rule (or set of rules) across all their service desk projects. Instead of having to add a new rule into each project individually.
Attachments
Issue Links
- duplicates
-
AUTO-117 Make it easier to manage Automation rules with multi-project scope, e.g. by adding a new scope based on "Project Category" or "Project Type", allowing non-site admins to manage global rules if their project is in scope
- Gathering Interest
- is duplicated by
-
AUTO-593 Non site admins are unable to update Multi-Project Automation rules (read-only)
- Closed
-
JSWCLOUD-22601 Allow permission to 'enable' or 'disable' automation rule to a project administrator for multi-project rule
- Closed
-
JSWCLOUD-22735 Allow non-Jira-administrator to have the ability to modify global Jira Automation rules
- Closed