Uploaded image for project: 'Automation for Cloud'
  1. Automation for Cloud
  2. AUTO-596

Allow More than Just "Groups" when Restricting Automation Rules with a "Manual" Trigger

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Duplicate
    • Trigger - Other
    • None
    • 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

      User Story

      As an Automation user, I would like to be able to restrict rules with a 'Manual' trigger to lists of users other than groups, because groups are not as useful to us as other lists.

      Context

      Groups can only be maintained by site admins, but can often involve a high level of maintenance burden; this "high effort from a small group of people" often leads organizations to not use them.

      However, the "manual" trigger's "restrict to" feature only works on groups.

       

      Allowing a list of individuals would be the minimum fix, but it would be really nice to also be able to:

      • Use project roles for project-scoped rules (Extending to global could be a nice-to-have, but I could see this getting sticky already).
      • A user picker or multi-user picker field
      • One or more team objects (if\when the "teams" re-brand\reinvention becomes reality)

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              78a5cd2342f3 Haddon Fisher
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: