---
title: "Streamline an approval process"
canonical: "https://support.appfire.com/space/JSUCLOUD/12518631/Streamline%20an%20approval%20process"
format: markdown
---
> Macro (aura-html)


---

| **Goal** | Save time and effort by streamlining approvals processes |
| --- | --- |
| **Scenario** | You want to eliminate unnecessary steps and downtime for those requesting approval, and those approving too. Use automation to automatically transition issues that don’t need approval and restrict the Approved action to selected users. |
| **JSU Components** | - [Follow Up Transition](https://appfire.atlassian.net/wiki/spaces/JSUCLOUD/pages/12518817) post function
- Value Field condition (Jira)
- [User is in any users ](https://appfire.atlassian.net/wiki/spaces/JSUCLOUD/pages/12518827)condition (JSU) |

## How to configure this rule

In this example, we are using an Approvals workflow that we configured for this use case. You can [re-create this workflow ](https://support.atlassian.com/jira-cloud-administration/docs/work-with-issue-workflows/)in your instance in a few minutes. The main feature of the workflow is that from the [submit] status, the issue can move to either [awaiting approval] or [approved].   


![Approval workflow in Jira](media://3c298f21-4254-4264-b470-66a01aad9195)

First, we want to set the criteria we'll use for determining what *requires approval*** **and what can be streamlined to be automatically *approved***.**

### Part 1: Add Value Field conditions for the Submit →  Awaiting Approval transition

1. Create a draft of your project workflow. If you're unsure how to get to this page, follow the onboarding steps in [Edit a Jira Workflow](https://appfire.atlassian.net/wiki/spaces/JSUCLOUD/pages/12519274). You can then view your workflow in Text or Diagram mode. The steps in this use case represent Diagram mode. If you haven't already, switch the workflow viewer to Diagram mode.
2. Select the transition (arrow) connecting the  [SUBMIT] and [AWAITING APPROVAL] statuses to display the transition rule options menu.
3. Select **Conditions** from the options list to display the *Conditions* tab.
4. Select **Add Condition**.
5. Select the *Value Field* condition, then select **Add** at the bottom of the page.
6. Now, let's configure the condition to ensure that only the desired issues can transition to [awaiting approval].
  1. **Field**: Select the field you want to inspect to determine if an approval can be streamlined for it. In our case, we have a field called `'Budget Required' that we've selected`.
  2. **Condition** - Choose the type of comparison you will use when comparing with the value. In our case, we want to require approval when the *Budget Required* is greater than (or equal to) 1,000. So we need to choose `greater-than-or-equal-to / >=`***.***
  3. **Value**: Type in the value you want to compare the field against. In our example, our chosen value is `1,000`***.***
  4. **Comparison Type**: To ensure that the value (a number) can be compared against the field (also a number), we need to specify that, in this scenario, the value is a `Number`***.***
7. Select **Add**. A preview of the condition we've just configured displays.
8. Publish the draft workflow. Now let’s configure a rule for the other transition.
9. Return to the Approvals workflow and create a draft again.
10. Select the transition (arrow) connecting the [submit] and [approved] statuses to display the transition rule Options menu.
11. Repeat steps 3-7, only in the case, we set the Condition** **field** **to less-than** **`<`*** ***to ensure that issues with a Budget Required of less than 1,000 can be moved to [Approved] instead of [awaiting approval].
12. Select **Add**. A preview of the condition we've just configured displays as with the previous condition.
13. Publish the draft workflow then move to Part 2.

### Part 2: Add the User is in any user condition for the Awaiting Approval → Approved transition

1. In the draft workflow, select the transition (arrow) connecting the  [AWAITING APPROVAL]  and [approved] statuses to display the transition rule options menu.
2. Select **Conditions** from the options list to display the *Conditions* tab.
3. Select **Add Condition**.
4. Select the *User is in Any Users* condition then select **Add** at the bottom of the page.
5. Add one or more users to the condition. Only the selected users can transition the issue.
6. Select **Add**.

### Part 3: Add JSU’s Followup Transition post function

1. Create another draft of the Approvals workflow.
2. In Diagram mode, select the transition (arrow) connecting [In progress] and [submit].
3. Select **Post Functions***** ***from the Options menu.
4. Select **Add post function** on the *Post Functions* tab.
5. Select *Follow Up Transition (JSU)* then select **Add** at the bottom of the page.
6. You do not need to configure the post function. Select **Add** again.
7. Publish the workflow.

### Test the rule and see the automation in action

1. Go to an open issue in your Approvals project. In our case, we have an issue currently in  [In progress] and with a *Budget Required*** **of 500.
2. Let's move the status to [submit].
3. The issue moves to the [submit] status, then a second (or two) later, automatically to the [approved] status.
  The issue history confirms this streamlined transition occurred.
4. Now try the same scenario, but where the *Budget Required *is 1,000, or more.
5. Let's move this issue to [submit] just like we did before.
6. Again, the issue is forwarded to its appropriate next transition; in this case, as the *Budget Required *value* *is greater-than-or-equal-to 1,000, it's moved to [awaiting approval]. Only the users named in the User is in Any User condition set up in Part 2 can select the Approved transition.
7. The issue history confirms that JSU helped us streamline the approvals here.