Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
  

Create a service request


You can create service requests in two ways:

Via the Self-Service Portal


To create a request, complete the steps below:

  1. Navigate to your Self-Service Portal and click Service Catalog.
  2. Fill in the fields.

    Tooltip
    onlyIcontrue
    appendIconinfo-filled
    iconColorblue

    The set of fields may differ, depending on the request templates.


  3. Click Save.

Via the agent interface


To create a request, complete the steps below:

  1. Navigate to Service Request Management → New.
  2. Fill in the fields.
  3. Click Save or Save and Exit.
Tip

You can copy the record number, title and link via the hamburger menu. To do this, click Generate link.

Request form fields

FieldMandatoryDescription
NumberYRequest number. The field is populated automatically with the unique identifier in the REQXXXXXXX format.
Master IT ServiceN

Assigned Master IT Service. The Master Service is the highest item in the service hierarchy.

CallerYSpecify the originator of the request.
CompanyNSpecify the company to which the request is related.
Contact TypeY

Select the source from which the request is received. Available options:

  • Phone
  • Email
  • Self-service
ServiceYSpecify the service affected by the request.
Related CIsNSpecify related configuration items affected by the request.
Assignment GroupY

Specify a user group responsible for working on the request.

Note

When the Assignment Group field is specified, the Assigned User field becomes non-mandatory for the states Registered and Assigned.

There is a dependency between the Assigned User and Assignment Group fields. To learn more, refer to the Restrictions for assignment article. 

Assigned UserY

Specify a user responsible for working on the request. This field is mandatory for the states In Progress, Completed and Closed.

Note

When the Assigned User field is specified, the Assignment Group field becomes non-mandatory for the states Registered and Assigned.

To reassign a user or a group, use the Reassign button at the top right corner of the window, or set a new assigned user, or a group by clicking the magnifier icon next to the Assigned User field. As a result, the request state changes to Assigned.

There is a dependency between the Assigned User and Assignment Group fields. To learn more, refer to the Restrictions for assignment article. 

Attention RequiredNSelect the checkbox to notify the line manager of the assigned group/assigned user.
SubjectYAdd a brief description of the request. After saving, the field is hidden on the form.
DescriptionNAdd a detailed description of the request.
Request TemplateNSelect the template created earlier.
StateN

This field displays the work state and progress. Available states:

  • Unprocessed
  • Processed
  • Dropped
External TaskN

Specify the task that the external company has to do.

Info

The field appears on the form when the state is External Processing. If the field is populated, it is displayed in other states.


External CompanyN

Specify the company that is going to complete the request task externally.

Info

The field appears on the form when the state is External Processing. If the field is populated, it is displayed in other states.


ImpactY

Measure the impact caused by the issue on the business processes. Available options:

  1. Low
  2. Medium
  3. High
  4. Very High
UrgencyY

Specify the urgency of the request. Typically, it is evaluated based on the time remaining until the issue impacts the business. Available options:

  1. Low
  2. Medium
  3. High
  4. Very High
PriorityN

Identifies the importance of the request according to the priority matrix. This field is populated automatically based on the values specified in the Impact and Urgency fields. Possible options:

  1. Low
  2. Moderate
  3. High
  4. Critical

See the Priority Management article to learn more.

Followers ListN

Displays a list of users who follow the problem for tracking the updates.

Info

This read-only field appears if at least one user followed the request.


State Flow


Closure

Procedure

StatusDescription
Logging

Registered

The state for a newly created service request. Possible transitions are In Progress, Authorization, Assigned, or Completed.
CategorizationAssignedA request is categorized and assigned to a relevant person or group.Categorization
AuthorizationA request must be reviewed and authorized by the responsible persons or groups.
ResolutionIn ProgressA request is in the process of implementation. When the work is over, the state has to be changed to Completed.
ClosureCompleted

When a request is in this state, a caller the caller (originator of the request) can perform the tests and provide feedback based on the results of the implementation. After this, change the state to Closed or If the user is satisfied with the solution, the request is marked as Closed; otherwise, it is Rejected by User. 

Also, when a request is completed, the caller can evaluate how the agent did his job and the service level as a whole. For this, the following steps need to be completed:

  1. The agent changes the request state to Completed.
  2. The caller receives a notification where he is they are asked to evaluate the agent's job and the service level.
  3. The caller follows the link in the notification and evaluates these parametersperform the evaluation. There are three values which correspond to three system values:
    1. Below Expectations
    2. Meets Expectations
    3. Above Expectations
Info

Rejected by User waiting status means that the caller is not satisfied with the work on the request.

ClosedAll activities on this service request are over and cannot be reopened.

Service

Requests Prioritization

requests prioritization


The priority of a Service Request service request can be figured out based on its impact and urgency using a the priority matrix.

The impact of a service request indicates the potential damage or effect that will be caused to the business user or , service, or CI. In SimpleOne, the impact metric can be categorized as:

  1. Low
  2. Medium
  3. High
  4. Very High.

The urgency of a service request indicates the measure of time until the issue impacts the business. In SimpleOne, the urgency metric can be categorized as:

  1. Low
  2. Medium
  3. High
  4. Very High.

Based on the priority, service requests can be categorized as:

  1. Low
  2. Moderate
  3. High
  4. Critical.

The priority matrix

Impact / UrgencyLowMediumHighVery High
LowLowLowModerateHigh
MediumLowModerateModerateHigh
HighModerateModerateHighCritical
Very HighHighHighCriticalCritical

Assigning and Updating Service Requests

Assign and update service requests


To

How to

assign a service request, follow these steps:

  1. Open the service request you need to assign.
  2. Click on the magnifier icon Image Removed Image Addednext to the Assigned User or the Assigned Group field.
  3. Select the responsible person or group to assign the service request to.
  4. Click Save or Save and Exit to apply the changes.
How to

There is also a quick way to assign a service request to a current user. To do so, click the Start work button in the right top corner to become the Assigned User. The state of the service request changes to In Progress automatically. The assigned group field remains unchanged (either with a group specified or empty). This button is available for all users who are not assigned to the service request and who have the itsm_agent role, or belong to the assigned group.

To update a service request, follow these steps:

  1. Open a the service request ;you need to update.
  2. Change the fields you want to update;as required.
  3. Click Save or Save and Exit to apply the changes.
Creating Request Tasks

Create request tasks


If solving a service request requires the participation of different departments, you can create a Request Task for each of them. For more information, please refer to the Request Task Management page article.

Creating Relationships

Create relationships


You can create relationships between service requests and other types of tasks. To do thisso, please complete the following steps:

  1. Open the service request you want to work on.
  2. Scroll down the page , then open the and open the Related Records tab.
  3. Click on the magnifier icon Image Removed Image Added next to the field you need.
  4. In the new window that appears, pick the required option you want.
  5. Click Save or Save and Exit to apply the changes.

Relationship Typestypes

TypeDescription
Slave RequestsPick a slave child request that your request will be is the master parent of.
Master RequestPick a master parent request that your request will be the slave foris the child of.
Related InquiryUser QueryA user query Inquiry related to the request.
Solved by ChangesThe request can be solved by the changes specified.
Related IncidentIncident An incident related to the request.
Related Request Model

Closure Information

A reference to the request model based on which the request is created. The field is read-only.

Closure information


Close the service request once it is completedOnce the service request has been fully processed, it has to be closed. When closing the service request, the responsible person must provide the closure code.

Closure code

This code specifies an option for the closure. SimpleOne has the following options: 

OptionDescription
Solved 1st 1st LevelSolved 1st Level - the request was The request is resolved by the 1st level of service agents of the 1st level without functional or hierarchical escalation.
Solved 2nd 2nd LevelThe request was is resolved by the service agents of the 2nd level of service agents (1st level of service agents was (agents of the 1st level were unable to solve it).
Not Solved (Refused)The caller wasn't is not satisfied with the service delivery.
Not Solved (Dropped)This closure code is chosen by the agent when the caller's request is not a service request.


Table of Contents
classfixedPosition