Uploaded image for project: 'Automation for Jira Server'
  1. Automation for Jira Server
  2. JIRAAUTOSERVER-516

Create security granularity to enable or disable triggers and actions per users or groups

XMLWordPrintable

    • 0
    • 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.

      Our latest release allows global administrators to lock down who can create project rules. You can remove permission altogether or simply use groups to determine who can and can’t create and edit project rules.

      However, allowing who can or not create automation tasks is not flexible enough for some customers, for example, who want their users to have the option to create automation but disable or enable specific triggers and actions for specific users or groups.

      Also, it would be good to have granular security to disable specific fields of actions, for example, who will be allowed to fill the values for From, From Name, and Reply to in actions like ‘Send email’.

      This will help customers to allow users to use Jira automation alone but restrict certain actions that do not work at the enterprise level.

              0291f5616540 Konrad Plasota
              1edd59bb2c95 Mateus
              Votes:
              9 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated: