| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This is the documentation |
...
for JSU for Jira Server/Data Center. If you are using JSU on Jira Cloud, |
...
see our JSU Cloud documentation. |
On this page:
|
Description
The 'Follow Up Transition' Post Function will evaluate post function evaluates the workflow conditions of all the next subsequent transitions on the target status of the current transition. If exactly one condition is valid, that the corresponding transition will be triggered as a 'follow up'followup.
Consider the following workflow:
...
- Our
The 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'
havestatus has a workflow condition:
'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 a user enters Number=3 during the ' Go ' transition, he will end up at the status the issue will transition to 'In Progress'. If he enters Similarly, if they enter 42, this the issue will lead him transition to 'Closed'.
In this example, we have been careful to configure our configured the workflow conditions so that always only and exactly 1 one condition can be true. Like this the user will never get 'stuck' at the 'Junction' state. Instead the 'Follow Up Transition' will lead him to the correct end state.
Tip: Since any The ‘Follow Up’ transition will always lead users to the correct status.
| Tip |
|---|
Any workflow condition can be used |
...
Configuration
You must specify the field and the desired value. For example:
...
for followups. |
Configuration
There are no mandatory parameters to configure for the Follow Up Transition post function. This post function is used in combination with your workflow conditions. You can select a user to act as the initiating user with the Perform As User option.
...
Perform As User
| Include Page | ||||
|---|---|---|---|---|
|
Position of the
...
post function
Ensure that this 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 post function is configured as the last post function.
...
| Info |
|---|
...
The transition triggered by the Follow Up Transition |
...
must not have |
...
an associated transition screen. (It is not shown to the user respectively.) In the example above, this means that the 'Under Five', 'Exactly Five' and 'Over Five' transitions |
...
must not have |
...
a transition screen. |
...
| Note |
|---|
The Follow Up Transition post function cannot be used in the Create transition (the one |
...
that is performed |
...
when a user creates a new issue). |
Conditions
However to To complete your setup, you have to configure at least one workflow conditionscondition. Let's continue the example from above, where a number field is evaluated. We will configure even 3 three conditions - ; one for each outgoing transition from the 'Junction' status.
Under Five
...
To add a condition, select Add condition on the Conditions tab. Here we are using the Value Field Conditioncondition from the JSU app . The details of its configuration looks as follows:
JSU.
...
Exactly Five
...
Over Five
...
Examples
Here are This section provides some more ideas , on how you might could use the 'Follow the Follow Up Transition ' Post Functionpost function.
Yes / No
A simpler more common use case is , that you have only 2 two transitions leading away and you evaluate basically from the triggering transition. You evaluate the same condition, but at one condition is negated.
a == b?
a != b?
Again you can use the Value Field Conditioncondition from the JSU app for JSU for this setup.
...
Check it: 'Follow Up Transition'
Post Functionpost function
Yes: Condition a == b?
No: Condition a != b?
Fast
...
forward
Some extra An additional step in your workflow might be only necessary if some a condition is not fulfilled. Otherwise ; otherwise, that step could be skipped.
...
Start: 'Follow Up Transition'
Post Functionpost function
Start Progress: Condition which must be fulfilled to skip the
'Extra Step'.
...
extra step
In this case, you do not have a 'Junction' state, status but instead, intend that the user can get 'stuck' should remain at the extra step until the condition is fulfilled.
Management
...
approval
See the Use Case /wiki/spaces/JSU/pages/12682131 for Conditional Approval use case for another real-life example.
Trouble shooting
...
Troubleshooting
Workflow remains in the Junction status
Not exactly one condition
...
You can usually identify the problem
...
by reviewing what the
...
post function
...
- If
is configured to do if exactly one condition is valid.
- that transition will be triggered
...
| Info |
|---|
Peform your analysis with the same user |
...
that |
...
remained in the Junction status. 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 such an issue, which got stuck in the Junction status: How many transition buttons does it have? Only if there is exactly one transition button, can the 'Follow up' will be triggered. If you have none or more than one transition button, you have to 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 the subsequent transition. For example, a validator could prevent the transition to get completed. Try (with the same user, who got stuck in Junction) to click that button to see what happensfrom getting completed.
Triggered transition fails
Another reason might a user may not be able to move past the Junction status could be that the triggered transition which is triggered does not run through. For example complete. This could be if it has a validator configured, which fails.