Uploaded image for project: 'Automation for Cloud'
  1. Automation for Cloud
  2. 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

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Unresolved
    • None
    • 4
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      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.

       

      Attachments

        Issue Links

          Activity

            People

              89403358cf11 Charlie Gavey
              ssreedhar@atlassian.com Shashank Sreedhar
              Votes:
              158 Vote for this issue
              Watchers:
              90 Start watching this issue

              Dates

                Created:
                Updated: