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

ITOps Automation: When using "User who triggers the event" allow rule to run for portal only user

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

      Issue Summary

      Currently, using "User who triggered the rule" in Legacy Automation rules behaves differently than "User who triggers the event" in Automation for Jira (A4J).

      In Legacy Automation when "User who triggered the rule" is used, the rule runs and goes through all the check even when rule is trigged by Customer (portal only account). While on A4J rule can only run if the user has all permissions.

      For example, 

      Legacy Automation rule comes with built-in rule called Comment updates reply status which can transition issue even when rule is triggered by Customer (portal only account). But we try to re-create this rule in A4J rule fails when it is triggered by Customer (portal only account) which does not have permission to access Jira.

      Suggestion

      Allow A4J rule to execute as customer similar to legacy automation

          Form Name

            [JSDCLOUD-12184] ITOps Automation: When using "User who triggers the event" allow rule to run for portal only user

              36bd3fea80e3 Makarand Gomashe
              3d70865c1864 Alim A.
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: