When OSWorkflow's Engine ends to perform a Transition, it checks all other available Transitions having this attribute set to true.
There is no need to use other mechanisms. Only few constraints and side effects are present :
Only Step Transitions are evaluated
The Auto-Transitions will share the same context as the first Transition, and you will see your comment added two times
Auto-Transition on Issue
The Auto-Transition on Issue has to be considered when :
we are able to define all conditions allowing or not the Auto-Transition to be launched,
and the initiator does not have to know which Transition has to be launched
To do that, the Transition definition :
has to qualify itself as reserved to Auto-Transition
has to specify all fields needed during the transition (present in Screen Transition)
may specify the Comment to apply on Transition
After, the initiator will have only to notify to the Auto Transition Manager which Issue has to be evaluated. It can be done :
using the Auto-Transition Service
using one of Auto-Transition Post-Function
using any Listener
Remote-Transition by Actions Id
The Remote-Transition by Actions Id has to be considered when :
we know exactly which Transition has to be launched,
and the initiator has to know the Transition by its Action Id.
To do that, the Transition definition does not require special settings ... The Initiator has only to notify to the Auto Transition Manager which Transition of an Issue has to be evaluated. It can be done :