The standard life cycle for User Requests tickets in iTop does not allow to assign a ticket to a Team without assigning it to a specific Person inside this Team. By creating a new state dispatched, this extension allows to dispatch a User Request ticket to a Team, without assigning it to particular Person. From the dispatched state the User Request can then be assigned to a Person.
Dispatch a User Request to a Team before assigning it to a Person.
The standard User Request life-cycle is the following:
Once the extension has been installed, the User Request life-cycle becomes as follows:
The definition of the TTO (Time To Own) metric is also modified to take into account the “dispatched” state (The Time To Own stops when the ticket is actually assigned to a Person, not only dispatched to a Team).
|2018-12-03||1.1.7||NL and ES translations|
|2018-07-02||1.1.5||ES and DE translations|
|2018-01-26||1.1.4||Update Russian translation (thanks to Vladimir Kunnin)|
|2017-10-27||1.1.3||Update German translation (thanks to ITOMIG GmbH)|
|2014-11-19||1.1.1||Adapted to iTop > 2.1.0, which gives more flexibility for developing other modules that could add states to the tickets|
|2014-03-11||1.0.1||Integration of the German translation (thanks to ITOMIG GmbH)|
extensionsfolder of iTop, and make sure that the folder can be read by the web server process.
This extension has no specific configuration setting.
A user must have either the profile “Service Desk Agent” or “Support Agent” (or Administrator) to be allowed to dispatch a ticket.