| Info |
|---|
This is the JSU for Jira Cloud documentation. If you are using JSU on Jira Server or on Jira Data Center, see our JSU Server/Data Center documentation. |
Description
The Follow Up Transition post function evaluates the workflow conditions of all the next transitions on the target status of the current transition. If exactly one condition is valid, that transition will be triggered as a follow-up.
Configuration
The Follow Up Transition post function does not have any additional parameters to configure, however, you must have a least one workflow condition configured.
Consider the following workflow:
...
Our issue has a mandatory number custom field.
At the end of the Go transition, we have configured a Follow Up Transition post function.
Each transition leading away from the status
has a workflow condition:Status colour Yellow title junction 'Under Five' has the condition: Number field < 5?
'Exactly Five' has the condition: Number field == 5?
'Over Five' has the condition: Number field > 5?
When the user performs the Go transition, this will always trigger a follow-up transition.
...
We have been careful to configure our workflow conditions so that always exactly only one condition can be true. This way, the user will never be stuck at the
| Status | ||||
|---|---|---|---|---|
|
Conditions
Let's continue the example from above, where a number field is evaluated. We will configure three conditions; one for each outgoing transition from the
| Status | ||||
|---|---|---|---|---|
|
Under Five
...
Exactly Five
...
Over Five
...
Simple Yes / No example
A simpler use case is when you have only two transitions leading away, and you evaluate the same condition; one condition is negated.
...
Check it: Follow Up Transition post function
Yes: Condition a == b?
No: Condition a != b?
Fast forward example
Some extra steps in your workflow might only be necessary if a condition is not fulfilled. Otherwise, that step could be skipped.
...
Management approval
See the Conditional Approval Process use case for another real-life example.
Asynchronous execution
| Include Page | ||||
|---|---|---|---|---|
|
Troubleshooting
Problem: Workflow is blocked at the Junction status
Cause: Not exactly one condition
Usually, the problem can be tracked down, by reviewing the expected outcome of the post function:
”If exactly one condition is valid, that transition will be triggered.”
...
If there is only one button, there might be something wrong with that following transition. For example, a validator could prevent the transition from getting completed. Try (with the same user, who got stuck in Junction) to click that button to see what happens.
Cause: Triggered transition fails
Another reason might be that the triggered transition does not run through. For example, if it has a validator that fails.
...