| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This is the documentation of JSU for Jira Server/Data Center. If you are using JSU on Jira Cloud, see our JSU Cloud 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'.
...
| Tip |
|---|
Since any workflow condition can be used for follow-ups, this provides great flexibility. |
Configuration
You must specify the field and the desired value. For example:
...
Perform As User
| Include Page | ||||
|---|---|---|---|---|
|
Position of the post function
There is not much to configure for the 'Follow Up Transition' post function. It does not have any parameters. Just ensure that it is the very last post function that will be performed, otherwise you will run into some problems.
...
You can see here the 'Follow Up Transition' Post Function configured as the last post function.
The transition triggered by the Follow Up Transition cannot have any transition screen. (It is not shown to the user respectively.) In the example above this means the 'Under Five', 'Exactly Five' and 'Over Five' transitions cannot have any transition screen.
The 'Follow Up Transition' Post Function cannot be used in the Create transition (the one which is performed, when a user creates a new issue).
Conditions
However to complete your setup, you have to configure at least one workflow conditions. Let's continue the example from above, where a number field is evaluated. We will configure even 3 conditions - one for each outgoing transition from the 'Junction' status.
Under Five
...
Here we are using the Value Field Condition from the JSU app. The details of its configuration looks as follows:
...
Exactly Five
...
Over Five
...
Examples
Here are some more ideas, on how you might use the 'Follow Up Transition' Post Function.
Yes / No
A simpler more common case is, that you have only 2 transitions leading away and you evaluate basically the same condition, but at one condition negated.
...
Check it: 'Follow Up Transition' Post Function
Yes: Condition a == b?
No: Condition a != b?
Fast Forward
Some extra step in your workflow might be only necessary if some condition is not fulfilled. Otherwise that step could be skipped.
...
So in this case you do not have a 'Junction' state, but instead, intend that the user can get 'stuck' at the extra step until the condition is fulfilled.
Management Approval
See the Conditional Approval use case for another real-life example.
Troubleshooting
My workflow gets stuck in the Junction status
Not exactly one condition
Usually, the problem can be tracked down by manually walking through what the post function would do:
...
If you now look at such an issue: 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.
Triggered transition fails
Another reason might be that the triggered transition does not run through. For example, if it has a validator configured, which fails.
...