| Info |
|---|
This is the documentation of JSU for Jira Cloud. 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 will evaluate the Workflow Conditionspost 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'.
Consider the following workflow:
...
Our issue has a mandatory number custom field.
At the end of the 'Go' transition, we have configured to 'a Follow Up Transition ' Post Functionpost function.
Each transition leading away from the status 'Junction' have 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.
For example, if the user enters Number=3 during the ' Go ' transition, they will end up at the status 'In Progress'this leads to the
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
We have been careful to configure our workflow conditions so that always exactly only and exactly one condition can be true. Like this, the This way, the user will never get 'be stuck ' at the 'Junction' state. Instead the 'Follow Up Transition' will lead them to the correct end stateat the
| Status | ||||
|---|---|---|---|---|
|
Configuration
The Follow -up Up Transition post function does not have any additional parameters to configure, however, you must have a least one workflow condition configured.
...
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 'Junction'
| Status | ||||
|---|---|---|---|---|
|
Under Five
...
Exactly Five
...
| Include Page | ||||
|---|---|---|---|---|
|
Examples
Here are some more ideas on how you might use the 'Follow Up Transition' Post Function.
Simple Yes / No example
A simpler more common use case is, that can apply when you have only two transitions leading away and you evaluate basically the same condition, but at one condition negated.
a == b?
Again you You can use the Value Field Condition Conditions Field conditions for this setup.
...
Check it: 'Follow Follow Up Transition ' Post Functionpost function
Yes: Condition a == b?
No: Condition a != b?
Fast
...
forward example
Some extra steps in your workflow might only be necessary if some a condition is not fulfilled. Otherwise, that step could be skipped.
...
Management
...
approval
See the Conditional Approval Process Use Case use case for another real-life example.
...
Usually, the problem can be tracked down, by manually walking through what the follow-up 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 got stuck in the Junction statusencountered the problem. There might be issues with permissions , that could lead to a different result, depending on the user performing the transition. |
If you now look at an issue that got stuck in 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 1 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.
...