Assign To Me

This extension adds a menu to directly assign any kind of ticket to the agent currently connected.

When a ticket is in a state where an agent can be assigned (or reassigned) to it, the extension adds the capability to directly assign (or reassign) the ticket to the person currently connected, through an additional option in the menu : “Assign to me”.

This feature can be deployed for any kind of ticket. This is is controlled by configuration parameters. By default, the extension enables the “Assign to me” feature to User Requests and Incidents.

For each class of ticket, the list of states where the “Assign to me” menu is available is defined through the configuration options. Furthermore, the stimulus that should be applied to the ticket in these given states to trigger the assign action is, as well, a configuration parameter.

The extension has been designed to be, as much as possible, independant from the datamodel. This is why, configuration parameters define, for each class of ticket, what state is concerned and what stimulus should be applied. Nevertheless, the extension has dependencies with attributes from the standard datamodel

• Agent ID in a ticket is supposed to be 'agent_id',
• The ticket is expected to handle a support team and this team's id is supposed to be 'team_id',
• The class lnkPersonToTeam is expected to be the class linking persons to teams.
• In order to properly handle the transitions where some attributes must change, must be prompted or are mandatory but currently null, the agent_id attribute must be set to “must prompt” or “must change” for these transitions. If this is not the case, the agent will not change during these transition…

The extension “Assign to me” requires the module iTop Tickets with at least version 2.2.0 and an auto dispatch module

'itop-auto-assignment/0.1.0||itop-auto-dispatch-ticket/0.1.0||combodo-autodispatch-ticket/1.0.2',

Use the Standard installation process for this extension.

Default configuration of the extension is done through XML. This configuration can be altered through XML and / or completed through the standard configuration file.

By default, the extension enables the “Assign to me” action to User Requests and Incidents and imposes that agent changes:

  <module_parameters>
    <parameters id="itop-assign-to-me" _delta="define">
      <agent_must_change type="bool">true</agent_must_change>
      <allowed_classes type="hash">
        <UserRequest type="hash">
          <dispatched>ev_assign</dispatched>
          <assigned>ev_reassign</assigned>
          <redispatched>ev_assign</redispatched>
        </UserRequest>
        <Incident type="hash">
          <dispatched>ev_assign</dispatched>
          <assigned>ev_reassign</assigned>
          <redispatched>ev_assign</redispatched>
        </Incident>
      </allowed_classes>
    </parameters>
  </module_parameters>

For each class of Ticket, the states where an assignment can be done are listed together with the stimulus triggering that action. These XML lines can be modified through XML customization like any other XML entry of iTop datamodel.

Should an iTop administrator wishes to enable the “Assign to me” action even if the agent won't change and to another type of tickets (like the simple change tickets), just add equivalent lines to the configuration file:

  'itop-assign-to-me' => array (
                'agent_must_change' => false,
                'allowed_classes' => array (
                  'Change' => 
                  array (
                    'new' => 'ev_assign',
                    'rejected' => 'ev_reopen',
                  ),
                ),
        ),

Some filters have been set to authorize, or not, the “Assign to me” action:

• The user should be different from the agent currently assigned to the ticket (this condition may be disabled though configuration, though),
• The user should have a profile that enables such action,
• The person linked to the connected user should belong to the team which the ticket is dispatched to,
• Configuration parameters should be consistent with the datamodel.

If these conditions are met and if the ticket is in a state where assignment to an agent can be done (as defined through the configuration), the “Assign to me” menu appears in the “Other Actions” menu available for your ticket.

Just select it and the stimulus defined in the configuration file will be applied. Note that action is directly done. No confirmation is required as long as the transition doesn't require some attributes, beside team_id and agent_id, to be changed, prompted or are mandatory but not set yet.

Q: Can an agent assign a pending ticket to him-self quickly, even if he is already the agent in charge?
A: Yes, since version 0.1.3, using the following configuration

Configuration

   'itop-assign-to-me' => array (
      'agent_must_change' => false,
      'allowed_classes' => array (
         'UserRequest' => array (
            'pending' => 'ev_assign',
            'assigned' => 'ev_reassign',
            'dispatched' => 'ev_assign',
            'redispatched' => 'ev_assign'
         ),
      ),
   ),

Q: Can I add an icon and a tooltip to this action?
A: Yes, overwrite the snippet:

Old piece of code:

AssignToMeMenuExtension

      $aResult = array(
                new SeparatorPopupMenuItem(),
                new URLPopupMenuItem(
                        $sMenu.' from '.$sTicketClass,
                        Dict::S($sMenu),
                        utils::GetAbsoluteUrlModulePage('itop-assign-to-me', 'assign-to-me.php', $aParams)
                ),
        );

New piece of code:

AssignToMeMenuExtension

     $oItem = new URLPopupMenuItem(
                 $sMenu.' from '.$sTicketClass,
                 Dict::S($sMenu),
                 utils::GetAbsoluteUrlModulePage('itop-assign-to-me', 'assign-to-me.php', $aParams)
     );
     $oItem->SetIconClass('fas fa-user-edit');
     $oItem->SetTooltip(Dict::S($sMenu."+"));
     $aResult = array(new SeparatorPopupMenuItem(), $oItem);