...
...
| 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. |
...
Consider the following workflow:
...
Our issue has a mandatory number custom field.
At the end of the 'Go' transition, we have configured to 'Follow Up Transition' Post Function.
Each transition leading away from the status 'Junction' have 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 user enters Number=3 during the 'Go' transition, he will end up at the status 'In Progress'. If he enters 42, this will lead him to 'Closed'.
...
Tip: Since any workflow condition can be used for the follow-ups, this provides you great flexibility. The JSU app has some quite useful additional 25680711 Follow Up Transition . But you might also use some other third-party app.
...
You must specify the field and the desired value. For example:
...
Perform As User
| Include Page | ||||
|---|---|---|---|---|
|
Position of the Post Function
There is actually not much to configure for the 'Follow Up Transition' Post Function. It does not have any parameters. Just make sure 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).
...
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.
...
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.
a == b?
a != b?
Again you can use the Value Field Condition from the JSU app for this setup.
...
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.
...
Start: 'Follow Up Transition' Post Function
Start Progress: Condition which must be fulfilled to skip the 'Extra Step'.
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.
...
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
It's important that you do your analysis with the same user, that got stuck in the Junction status. There might be issues with permissions, that could lead to a different result, depending on the user performing the transition.
...