You can use the Minimum Required approbations and rejections rules to specify if the approval step can be considered approved or rejected based on subset of stakeholders reply.
You are able to create multiple rules based on conditions or unconditioned.
Rules based on conditions expect a valid Jql statement that can be created via the Conditional Rules Administration screen.
For example, you might need that the purchase requests having an amount in a certain range require different numbers of approbations and rejections.
To set up a Minimum Required approbations and rejections based on condition, go to
And finally you might need that the purchase requests having an amount not included in the ranges above require a different numbers of approbations and rejections.
In this case you can set up Minimum Required approbations and rejections unconditioned that will be considered only if the previous conditions are not satisfied.
To set up a Minimum Required approbations and rejections based unconditioned, go to
For example, case of purchase requests requiring the following
- for expenses greater then
- the approval step can be considered approved if All stakeholders approve
- the approval step can be considered rejected if 1 stakeholder reject
- for expenses in the range
- the approval step can be considered approved if it receives the 50% of approbations
- the approval step can be considered rejected if it receives the 50% of rejections
- for expenses that are less than $100
- the approval step can be considered approved if it receives 1 approbation
- the approval step can be considered rejected if All stakeholders reject
The Minimum Required approbations and rejections based on conditions are evaluated always before of any Minimum Required approbations and rejections unconditioned.
It implies that, If the Condition associated to a Minimum required approbation is true, the Minimum required approbation unconditioned is not evaluated.
For example, in the following case, when the priority is high, the approval step is considered approved only when all required approvals are approved.
When the priority is not high, it's not required any approbation.
The Minimum Required approbations and rejections based on conditions are evaluated basing on their sequential order.
It implies that, If the condition associated to the top Minimum required approbation is true, the next Minimum required approbation is not considered also if the associated condition is true.
For example, in the following case, when the amount is less then $500, the approval step is considered approved only when 1 approval is approved.
When the priority is not high, it's not required any approbation.
The Minimum Required approbations and the Minimum Required rejections are evaluated independently.
It implies that case of either the Minimum required approbations and the Minimum Required approbations rejections are satisfied the approval step can be considered approved or rejected same time.
In this case, if an Automatic Workflow transition must succeed and the minimum required approbations and rejections are conditioned, their sequential order is considered.
The established sequential order to check the rules is shown in parentheses.
For example, in the following case, when the amount is less then $1000, the approval step is considered approved if 1 approval is approved and it is considered rejected if 1 approval is rejected.
Case of an approbation and a rejection arrive at the same time, the approval step will be considered rejected due to the established order to evaluate the rules.
