-
Suggestion
-
Resolution: Unresolved
-
None
-
0
-
Suggested improvements
- Currently, the project scope options available in the automation use references with a project that is deleted and which requires manual intervention in removing the deleted project from the rule. Hence, it would be nice to have a new project scope option in the automation rule which is based on "project category".
- Ability for project admins to copy rule from one project to another - It would be awesome to have the ability for project admins to copy rules from one project to another without going to the global automation page.
- Ability to exclude the projects from the rule scope - It would be beneficial to add an additional scope option, "All projects excluding specific ones." This would enable users to apply a rule to all projects except for a select few, such as restricting 3-4 projects from running the rule. This would be helpful to optimize the rule executions globally.
- duplicates
-
- Closed
- is duplicated by
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Closed
-
- Gathering Interest
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
[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
We also see this as a important feature to reduce maintenance for central Jira admins.
I agree. If this turns out to be a feature that is kept behind an Enterprise paywall I'll be incredibly disappointed.
I'm not sure how much of a fan I am of the label RIBS-SHORT being removed and "enterprise" being added.
Many organisations create "template projects" with the correct project configuration, and create new projects with shared configurations of these template projects. Being able to automatically add new projects to an automation rule's scope through project category-scope, would really ease the project creation process by removing an manual step, where you might easily forget adding the new project to a single rule's scope.
This should go to the top of the list.
It's a lot of manual work to update 100+ automations upon the creation of 1 project.
I have to comment on this again because it's wild that this feature doesn't exist yet and it's in Gathering Interest for 3 years.
I now have rules that cover 25 projects each (I'm admin on all projects), our Jira Admin has made me the owner of these multi-project rules but I cannot edit any of them, can't even change their label.
This week, one of the rules kept sending failure emails to me but I cannot access the "global" audit log like Jira Admins can - my Audit log depends on which of the 25 projects I'm currently in so it will only show me the rule runs triggered by that specific project. I can't see where it's failing so I have to raise another ticket to our Jira Admins to check and fix.
It is such a waste of time and unnecessary burden on Jira Admins. Just let me manage multi-project rules for projects that I admin. If I can be made owner of the rule, why can't I edit that rule?
We really need this.
This is actively preventing us from expanding our use of Automation and is making product adoption slower and more difficult than it would otherwise have been.
Manager: My teams need this and that, can we make that happen?
Me: Yeah sure, technically we can, but it's going to be a nightmare to administrate
Manager: Goes back to tracking things in spreadsheets.
Much needed feature here - can we have an Atlassian PM from automation chime in on what the future looks like for this request?
As a project admin of 12 projects that are all part of the same product portfolio - this is so frustrating. Really hope Atlassian would prioritize this idea.
So overdue!