Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-2095

Allow automation rules to be run as a non-agent user

    XMLWordPrintable

Details

    • 4
    • 21
    • 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

      With the new automation engine in Jira Service Management - this is now possible! Please see the documentation linked here on how to change the rule actor for the automation rules: https://support.atlassian.com/jira-software-cloud/docs/run-rules-as-another-user/

      To get to the new Automation engine, simply go to your project settings and select Automation. The existing automation have been renamed legacy automation.

      NOTE: This suggestion is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding suggestion.

      The current automation functionality of Service Desk provides the option to perform automated transitions based on a set of rules.
      In some situations, it is required to have such transitions being displayed as performed by an automated user.
      The current implementation only allows this to be performed by the project lead, or the user triggering the event.
      A separate user can be created to function as an automation user, and set as the project lead, this however will require a Service Desk license in order to function.
      Can functionality get provided to allow automated functions of Service Desk be performed by a system user without using a license slot?

      Attachments

        Issue Links

          Activity

            People

              vwong@atlassian.com vwong
              mnassette MJ (Inactive)
              Votes:
              69 Vote for this issue
              Watchers:
              56 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: