Description

The 'Follow Up Transition' Post Function will evaluate 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 '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'.

In this example, we have been careful to configure our workflow conditions so that always only and exactly 1 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 workflow condition can be used for the follow ups, this provides you great flexibility. The JSU app has some quite useful additional Follow Up Transition . But you might also use some of another third party app.

Configuration

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 'Follow Up Transition' Post Function cannot be used in the Create transition (the one which is performed, when a user creates a new issue).

Conditions

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.

Yes / No

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.

Management Approval

See the Use Case /wiki/spaces/JSU/pages/12682131 for another real life example.