| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This is the documentation of JSU for Jira Server/Data Center. If you are using JSU on Jira Cloud, you can find the documentation here. |
...
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.
...
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).
...
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, how you might use the 'Follow Up Transition' Post Function.
...
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?
...
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'.
...