User Tools

Site Tools


extensions:combodo_dispatch_userrequest_1_0

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

extensions:combodo_dispatch_userrequest_1_0 [2018/12/19 11:40] (current)
Line 1: Line 1:
 +====== Dispatch User Request ======
 +---- dataentry summary ----
 +name             : Dispatch User Request
 +index_hidden ​    : no
 +version ​         : 1.0.1
 +release_dt ​      : 2014-03-11
 +description_wiki : Add an additional state '​dispatched'​ to User Requests
 +itop-versions ​   : 2.0
 +keyword_tags ​    : Helpdesk, UserRequest,​ life-cycle, process
 +dependencies_s ​  : itop-config-mgmt
 +author ​          : Combodo
 +download_url ​    : http://​www.combodo.com/​itop-extensions/​dispatch-userrequest-1.0.1-12.zip
 +alternate-name ​  : ​
 +----
 +
 +<​related_components>​Other versions of this component:</​related_components>​
 +
 +
 +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.
 +
 +
 +===== Features =====
 +
 +Dispatch a User Request to a Team before assigning it to a Person.
 +
 +The standard User Request life-cycle is the following:
 +
 +{{:​extensions:​userrequest-std-lifecycle.png?​600|Standard User Request Life-cycle}}
 +
 +Once the extension has been installed, the User Request life-cycle becomes as follows:
 +
 +{{:​extensions:​userrequest-modified-lifecycle.png?​600|User Request Life-cycle with "​dispatched"​ state}}
 +
 +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).
 +
 +<note tip>​Actually two new states are added to the life-cycle: //​dispatched//​ and //​redispatched//,​ to take into account the first assignment of a ticket. When a ticket which was assigned to a Person is dispatched again to a Team, the agent to which the ticket was assigned is cleared (even if the ticket is dispatched again to the same team).</​note>​
 +
 +
 +===== Revision History =====
 +
 +^  Version ​ ^  Release Date  ^  Comment ​ ^
 +|  1.0.1  |  2014-03-11 ​ | Integration of the German translation (thanks to ITOMIG GmbH) |
 +|  1.0.0  |  2014-02-28 ​ | First version |
 +
 +
 +===== Installation =====
 +
 +  - Expand the zip file of the extension and copy the folder ''​combodo-dispatch-userrequest''​ into the ''​extensions''​ folder 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 <​nowiki>​http://<​itop>/​setup/</​nowiki>​
 +  - When prompted to select the extensions to install, check "​Dispatch of User Requests"​ and complete the setup.
 +{{:​extensions:​dispatch-userrequest-install.png?​450|Installation screen}}
 +
 +===== Configuration =====
 +
 +This extension has no specific configuration setting.
 +
 +===== Usage =====
 +
 +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:
 +{{:​extensions:​dispatch-userrequest-new-button.png?​600|New button "​Dispatch to a team"​}}
 +
 +On an User Request in state //new//, the action "​Dispatch to a team.."​ is available in the drop-down list of actions.
 +{{:​extensions:​dispatch-userrequest-popup-menu.png|New action "​Dispatch to a team"​}}
 +
 +A user must have either the profile "​Service Desk Agent" or "​Support Agent" (or Administrator) to be allowed to dispatch a ticket.
 +
 +<note tip>The list of teams to which the ticket can be dispatched are the same as the ones used when assigning the ticket directly to a Team and a Person. The possible Teams are defined by the Delivery Model of the Organization of the ticket.</​note>​
  
extensions/combodo_dispatch_userrequest_1_0.txt ยท Last modified: 2018/12/19 11:40 (external edit)

";