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

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Unresolved
    • Component/s: 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.

       

            Assignee:
            Scott Bell
            Reporter:
            Shashank Sreedhar
            Votes:
            319 Vote for this issue
            Watchers:
            181 Start watching this issue

              Created:
              Updated: