Info |
---|
This is the JSU for Jira Cloud documentation. If you are using JSU on Jira Server or on Jira Data Center, see our JSU Server/Data Center documentation. |
Description
The ‘Follow Follow Up Transition’ Transition post function evaluates the workflow conditions of all the next transitions on the target status of the current transition. If exactly one condition transition is validpossible, that transition will be triggered as a follow-up. If more than one transition is possible, JSU cannot determine which to use as the follow up transition.
To learn more about global transitions in Jira workflows, see Atlassian’s advanced workflows documentation.
Configuration
The ‘Follow Follow Up Transition’ Transition post function does not have any has no additional parameters to configure; however, you must have a at least one workflow condition configured.
...
Our issue has a mandatory number custom field.
At the end of the Go transition, we have configured a ‘Follow Up’ Follow Up Transition post function.
Each transition leading away from the 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, this leads to the
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
We have been careful to configure configured our workflow conditions so that always exactly only one condition can be true. This way, the user will never be stuck at the
Status | ||||
---|---|---|---|---|
|
...
A simpler use case is when you have there are only two transitions leading away , and you evaluate the same condition; one condition is negated.
...
When using post functions that create issues or follow-up transitions, consider the outcome of the rule and the user permissions of your project teams. You can also use preconditions to restrict when rules are run to reduce the likelihood of causing an infinite loop. Learn more about how JSU identifies an infinite loop in Infinite Loop Detection.