Problem Definition

Managing workflow transitions can become a hurdle depending on how complex your workflow is and how many transitions exist in the workflow.
If you would like all of the transitions sharing similar configuration, but still having their own specifics, you would need to manage properties of each transition individually.

The only option an administrator have at the moment would be to use the same transition on all steps associated to the same target status.

If all transitions in a workflow shares the same configuration for Triggers, Conditions and Validators, but each require a different setup for Post functions, then the only option is to individually configure each transition.

In case of a change on the shared configuration, the administrator needs to apply the same configuration on all transitions.

Suggested Solution

There could be some sort of inheritance functionality for workflow transitions.
For example, we could have a base transition configuration and derived transitions, on which the later would inherit configuration from the former.