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
- via the agent interface
Via the Self-Service Portal
To create a request, complete the steps below:
- Navigate to your Self-Service Portal and click Service Catalog.
Fill in the fields.
Tooltip onlyIcon true appendIcon info-filled iconColor blue The set of fields may differ, depending on the request templates.
- Click Save.
Via the agent interface
To create a request, complete the steps below:
- Navigate to Service Request Management → New.
- Fill in the fields.
- 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
Field | Mandatory | Description | ||
---|---|---|---|---|
Number | Y | Request number. The field is populated automatically with the unique identifier in the REQXXXXXXX format. | ||
Master IT Service | N | Assigned Master IT Service. The Master Service is the highest item in the service hierarchy. | ||
Caller | Y | Specify the originator of the request. | ||
Company | N | Specify the company to which the request is related. | ||
Contact Type | Y | Select the source from which the request is received. Available options:
| ||
Service | Y | Specify the service affected by the request. | ||
Related CIs | N | Specify related configuration items affected by the request. | ||
Assignment Group | Y | Specify a user group responsible for working on the request.
There is a dependency between the Assigned User and Assignment Group fields. To learn more, refer to the Restrictions for assignment article. | ||
Assigned User | Y | Specify a user responsible for working on the request. This field is mandatory for the states In Progress, Completed and Closed.
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 Required | N | Select the checkbox to notify the line manager of the assigned group/assigned user. | ||
Subject | Y | Add a brief description of the request. After saving, the field is hidden on the form. | ||
Description | N | Add a detailed description of the request. | ||
Request Template | N | Select the template created earlier. | ||
State | N | This field displays the work state and progress. Available states:
| ||
External Task | N | Specify the task that the external company has to do.
| ||
External Company | N | Specify the company that is going to complete the request task externally.
| ||
Impact | Y | Measure the impact caused by the issue on the business processes. Available options:
| ||
Urgency | Y | Specify the urgency of the request. Typically, it is evaluated based on the time remaining until the issue impacts the business. Available options:
| ||
Priority | N | 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:
See the Priority Management article to learn more. | ||
Followers List | N | Displays a list of users who follow the problem for tracking the updates.
|
State Flow
Procedure | Status | Description | ||
---|---|---|---|---|
Logging | Registered | The state for a newly created service request. Possible transitions are In Progress, Authorization, Assigned, or Completed. | ||
Categorization | Assigned | A request is categorized and assigned to a relevant person or group. | ||
Categorization | Authorization | A request must be reviewed and authorized by the responsible persons or groups. | ||
Resolution | In Progress | A request is in the process of implementation. When the work is over, the state has to be changed to Completed. | ||
Closure | Completed | When a request is in this state, a caller the caller (originator of the request) can perform the tests and give provide feedback by based on the results of the implementing. After this, change the state to Closed or implementation. 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 completingcompleted, the caller can evaluate how the agent did his job and the service level in the as a whole. For this, the following steps need to be completed:
| ||
Closure | Closed | All the activities on this service request are over , and it cannot be reopened. |
Service
Requests Prioritizationrequests 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:
- Low
- Medium
- High
- 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:
- Low
- Medium
- High
- Very High.
Based on the priority, service requests can be categorized as:
- Low
- Moderate
- High
- Critical.
The priority matrix
Impact / Urgency | Low | Medium | High | Very High |
---|---|---|---|---|
Low | Low | Low | Moderate | High |
Medium | Low | Moderate | Moderate | High |
High | Moderate | Moderate | High | Critical |
Very High | High | High | Critical | Critical |
Assigning and Updating Service Requests
Assign and update service requests
To
How toassign a service request, follow these steps:
- Open a the service request you need to assign;.
- Click a the magnifier icon in the
Image Addednext to the Assigned User or the Assigned Group field;.
- Select the responsible person or group to assign the service request ;to.
- Click Save or Save and Exit to apply the changes.
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:
- Open a the service request ;you need to update.
- Change the fields you want to update;as required.
- Click Save or Save and Exit to apply the changes.
Create request tasks
If solving of 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 RelationshipsCreate relationships
You can create relationships between service requests and other types of tasks. For thisTo do so, please complete the following steps:
- Open the service request you want to work on;.
- Scroll down the page , then open the and open the Related Records tab;.
- Click a the magnifier icon in
Image Added next to the field needed;you need.
- In the new window appearedthat appears, pick an option you want;the required option.
- Click Save or Save and Exit to apply the changes.
Relationship Typestypes
Type | Description |
---|---|
Slave RequestRequests | Pick a slave child request that your request will be is the master parent of. |
Master Request | Pick a master parent request that your request will be the slave foris the child of. |
Related User Query | A user query related to the request. |
Solved by Changes | The request can be solved by the Changes changes specified. |
Related Incident | An incident that have a relation related to the request. |
Closure Information
Related Request Model | 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 completedWhen 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 of for the closure. SimpleOne has the following options:
Option | Description |
---|---|
Solved 1st 1st Level | Solved 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 Level | The 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 | ||
---|---|---|
|