Basically, in JIRA, is considered as Auto-Transition, any Workfow Transition where its Initiator is not directly raised by the user through the UI.
In JIRA Community, there are different ways to implement an Auto-Transition, where different definitions of Auto-Transition coexist.
You will see Auto Transition done
To implement Auto-Transitions, you have to identify
And then, you will be able to decide How to implement your Auto-Transition.
To cover these features, Minyaa provides different mechanisms ...
Some Use Cases where Auto-Transition may be encountered :
|Auto-Triage||A priority is applied depending different fields||Automatic Actions|
|Auto-Assignment||A user is assigned depending different fields (other than Component)||Automatic Actions|
|Need more Information||As soon as a new comment is added by the reporter/customer, the issue has to passed to the next step||Auto-Transition initiated from a Listener|
|Inactivity||No activity on the issue (Comment, Transition, Worklog, Edit) since a specified delay||Auto-Transition initiated from a Auto-Transition Service|
|Auto-Close of linked Issue||On Issue Close, we want see linked Issue, also closed.||Remote-Transition initiated from a Auto-Transition Post-Function|
You should be able to find the good implementation to resolve your own Use Case ...
Discover Auto-Transition Management and imagine how you will be able to improve your workflows.
On this page:
See also ...