Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

In a separate part of our documentation, we demonstrated how users could set up a required approval process and showed how to enable and disable the Submit Order button depending on the approval state.

In this document, we’ll show an approval process may be set up to require approvals for all orders over a certain value, say $500. Our goal is that any order totaling less than $500 is automatically approved while placing an order of $500+ will cause the Submit Order button to be disabled until the order is approved.

Let’s take a look at how this can be accomplished.

Instructions

To make any workflow changes necessary, users will need Jira administration permissions.

To set up the Checkout automation rules, the user will need project administrator permissions.

Configuring the workflow

First, you will need to set up the workflow which will be used for the Checkout issue type. If the Checkout project was created with the IT Service Desk template, an approval workflow should already exist, but it may not be in use for the Checkout issue type. It will be named in the form of project-key: Service Request Fulfillment with Approvals workflow for Jira Service Desk.

To use it on the Checkout issue type, modify the project workflow scheme and assign the chosen workflow to the Checkout issue type.

Once the workflow has been assigned to the Checkout project, edit the workflow and click on the Waiting for Approval status, and select Add approval.

You’ll need to select the custom field which will be used to set the approvers. Please be aware if you use the Approvers field, Checkout will automatically add the department head for the order as an approver when the ticket is created. If you do not want that behavior, you will need to create a custom approvers field.

Once the workflow has been configured how you like it, we can move onto the next portion.

Configuring the Automations

Setting up an optional approval process requires us to configure two separate Checkout automation rules.

  1. This rule will automatically approve orders totaling less than $500 and disable the Submit Order button for orders totaling $500+.

  2. This rule will enable the Submit Order button if the request is approved.

To create an automation rule, navigate to Project Settings > Checkout > Automation and click on Create Rule.

Set up the rule with the following settings:

The next rule we set up will re-enable the Submit Order button if the order is approved. Create a new rule with the following configurations:

These two automation rules will make sure that all orders which require an approval get one. A final touch we can add is setting up a third automation rule to move all Items to the Declined status if the order is declined by the approver.

To do so, we’ll create a new rule with the following configurations:

Image Added
Note

Please double check to make sure you choose the trigger “Request Declined” with a capital “D”. We have a known issue with two triggers being named very similarly.

Filter by label (Content by label)
showLabelsfalse
showSpacefalse
cqllabel = "approvals"

Page Properties
hiddentrue

Related issues

Write into our Support Desk with any questions you have.