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

Better support for approval workflows in Automation, e.g. add a smartvalue for JSM approval buttons in Automation

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • 38
    • 30
    • 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.

      Suggested improvements

      • Having a smartvalue for approval buttons in Automation would allow us to create customised emails for approvals for specific situations which require more information or specific details which are not necessary for other approvals in the same project.
      • Using the Approval completed trigger in Automation, additional attributes for approval.approver don't exist
      • However, in the case of 2 approvers, when one of the approvers already takes an action on the ticket (either approve or reject), the system still includes that tickets in the pending list of the reminder notification email, hence causing quite a confusion to that approver who took the action. So we are wondering if there's a way where the system can recognize the action of the approver on a specific ticket, then eliminate that ticket from the list of reminder notification email. Could you help us with a suggestion?
      • Ability to have multiple approval steps with multiple approval groups applicable in an Automation Rule. So one group per status in the Workflow, but when the approval is completed it moves to the next status, depending on if it is rejected or approved. The Automation Rule would account for this scenario and choose to move to one status or another if they are rejected or approved and continue on if there are multiple statuses with approvals and the rule would allow for auto transitioning to the next status.
      • As of now, automation rules using the Approval required trigger will only be executed when an issue is created having at least one approver, or when an approver is added to the issue. This trigger should recognize when an issue requires approval even if there are no approvers added, based on the workflow configuration.

              36bd3fea80e3 Makarand Gomashe
              79302268a842 Ana Viseu (Inactive)
              Votes:
              73 Vote for this issue
              Watchers:
              43 Start watching this issue

                Created:
                Updated: