...
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 | ||||
|---|---|---|---|---|
|
...
The Follow Up Transition post function does not have any additional parameters to configure, however, you must have a least one workflow condition configured.
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
...
Asynchronous Execution
...
Simple Yes / No example
A simpler use case is , can apply when you have only two transitions leading away and you evaluate basically the same condition, but at ; one condition is negated.
a == b?
You can use the Value Jira’s Value Field conditions for this setup.
...
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 manually walking through what reviewing the expected outcome of the post function would do:
...
”If exactly one condition is valid
...
, that transition will be triggered.”
| Info |
|---|
It's important that you do your analysis with the same user that encountered the problem. There might be issues with permissions that could lead to a different result, depending on the user performing the transition. |
If you look at an issue that got stuck in blocked at the Junction status: How many transition buttons does it have? Only if there is exactly one transition button, 'Follow up' will be triggered. If you have none or more than one transition button, you must review your workflow conditions on the transitions leading out from the Junction status.
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 configured, which failsthat fails.
| Tip |
|---|
You can learn more about workflow validators in Atlassian’s Configure Advanced Issue Workflows article. |