Create request tasks

If solving a service request requires the participation of different departments, an agent can create a request task for each of them. Dividing requests into tasks has several benefits, such as the ability to assign different request tasks to different employees and to get tasks done simultaneously, or one after another. Service requests and request tasks are in the parent-child relationship.

To create a request task, follow the steps below:

1. Navigate to Service Request Management → All Service Requests.
2. Open the service request you want to create a request task for.
3. In the Related Lists area, select the Request Tasks tab and click New.
4. Fill in the fields.
5. Click Save or Save and Exit to apply the changes.

You can create as many requests tasks as you need.

Request Tasks form fields

Field	Mandatory	Description
Number	Y	This field is populated automatically and has the RQTSKXXXXXXX format.
Request	Y	Specify the request that you need to divide into request tasks.
Subject	Y	Add a brief description of the request task.
Description	N	Add a detailed description of the request task.
Followers list	N	Specify the users to receive notifications, when: A Work note is added to the activity feed;  The record state changes; The value of the fields Assignment Group, Assigned User changes; The agent adds or deletes a follower.  The users will not receive notifications when a user Follows or Unfollows the record on their own using a corresponding UI-action on the form.  The field is read-only when the record is in the Canceled or Closed state.
State	Y	Specify the state of the request task. Available options: Waiting for Request Authorization  Registered  In Progress  Completed  Closed  Canceled The Waiting for Request Authorization state is displayed when the related service request is in the Authorization state. Once the service request is authorized, the task state changes to Registered. The Closed state appears only when the request task is in the Completed state.
Assignment Group	Y	Specify a responsible group to work on the request task. When a request task is assigned to a responsible group, the Assigned User field becomes non-mandatory if the related service request is in the Registered or Assigned state. There is a dependency between the Assigned User and Assignment Group fields. Refer to the Auto Assignment article to learn more.
Assigned User	Y	Specify a responsible user to work on the request task. When a request task is assigned to a responsible user, the Assigned Group field becomes non-mandatory if the related service request is in the Registered or Assigned state. 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. Refer to the Auto Assignment article to learn more.
Activity Feed
This section appears after the request task is saved.
Work notes	N	Add work notes. The field becomes mandatory when: the assigned user changes the task state to Completed, Canceled, or Closed. another user with the ITSM_agent role changes the values of the State, Assignment group, or Assigned user fields.

Follow / Unfollow UI-actions are available on the form. If you click Follow, you will be added to the Followers list and start receiving notifications. If you click Unfollow, you will stop receiving notifications about the changes in the record.

Access to the form fields

---

The read or update access to certain fields of a record can vary depending on the current user's roles.

• The users with the ITSM_agent or request_manager roles, other than the creator of the service request task or the assigned user, can:
  • View the record.
  • Submit Work notes in all states of the service request task other than Closed.
  • Edit the Followers list field value.
  • Edit the State, Assignment group, and Assigned user field values in all states of the service request task. The Work notes field becomes mandatory in this case.
• The caller can:
  • View the record, except for the Work notes field.

Request task state model

---

Timepoint indications

An indication is a time counter automatically generated when the indicator start conditions are met. It shows all primary timings, time points, and the current state of the SLA for a particular record (an incident, a request, and other), which allows you to track the level of the service quality target indicators. On the Timepoint Indication tab in the Related Lists area for a service request, you can check the service request indication. For more information, see Manage Indications.

Create relationships

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

1. Navigate to Service Request Management → All Requests and open the service request you want to work on.
2. Open the Related Records tab.
3. Click the magnifier icon next to the respective field.
4. In the window that appears, choose the necessary option.
5. Click Save or Save and Exit to apply the changes.

Relationship types

Type	Description
Request Template	Template that this request is based on.
Level of Dependency	Specify the level of dependency: Parent or Child.
Child Request	Select a child request that your request is the parent of.
Parent Request	Select a parent request that your request is the child for.
Solved by Changes	Request can be solved by the changes specified.
Related User Query	User query related to the request.
Related Incident	Incident related to the request.
Related Request Model	Contains a reference to the request model based on which the request is created. The field is read-only.