Dispatch User Request
- Dispatch User Request
- Add an additional state 'dispatched' to User Requests
- Helpdesk, UserRequest, life-cycle, process
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).
|1.0.1||2014-03-11||Integration of the German translation (thanks to ITOMIG GmbH)|
Expand the zip file of the extension and copy the folder
extensionsfolder of iTop, and make sure that the folder can be read by the web server process.
If iTop is already installed, make sure that the configuration file is not read-only
Launch the setup program by pointing your browser to http://<itop>/setup/
When prompted to select the extensions to install, check “Dispatch of User Requests” and complete the setup.
This extension has no specific configuration setting.
The new dispatched state is fully integrated with the life-cycle of the ticket. For example, when creating a new User Request, an extra button “Dispatch to a team” appears:
On an User Request in state new, the action “Dispatch to a team..” is available in the drop-down list of actions.
A user must have either the profile “Service Desk Agent” or “Support Agent” (or Administrator) to be allowed to dispatch a ticket.