This documentation applies to the 8.1 version of Service Desk, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

Tasks overview

A task is a unit of work that needs to be completed as a step in resolving an incident request. If the solution to an incident request involves more than one action, procedure, or process, consider dividing the solution into separate tasks. Dividing the solution into separate tasks can help you to better manage and to monitor the incident request as it moves toward resolution.

You can assign the tasks to the same person, to several people, or to a support group. The person or support group to whom the task is assigned is the task implementer.

When the group coordinator sets the task status to Work in Progress, the task implementers are notified of the tasks assigned to them by email, pager, or some additional means. After a task is assigned to the task implementers, they can log their progress as they complete each task.

You can use a task template to add a task to an incident request, or you can create an ad hoc task. Task templates are predefined tasks that you can quickly add to an incident request.

When using task templates, you can also add tasks that are divided into sub-tasks. A task that has sub-tasks is called a task group. The sub-tasks of the task group are called "children" of the task group.

An ad hoc task is any task that is not included in the list of task templates. You create ad hoc tasks manually.

Although tasks and task groups are related to specific incident request records, information about the tasks and task groups is stored on a separate Task form. You can relate an unlimited number of tasks or task groups to an incident request.

After a task or task group is assigned to a task implementer, the task implementer receives notifications to perform each of the assigned tasks.

 

Note

After adding tasks to a request, if you do not save the request, or due to other issues, if the request is not created, the tasks related to the request are not deleted. These tasks are saved as orphaned tasks in the system.

However, the escalation SYS:CLN:TA@00:05-StartCleanup which is run every 24 hours deletes any tasks that are in Inactive state longer than a defined retention period, and do not have any parent record associated with it.


Related topics

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments

  1. Howard Robinson

    The Note that mentions that tasks can be Assigned only if the associated incident is Assigned is incorrect. The incident needs to be In Progress.

    Dec 05, 2013 04:46
    1. Bruce Cane

      Thanks for bringing this to our attention, Howard. Just to confirm, is the following text correct: 

      Tasks can have an Assigned status only if the associated incident request also has the status of In Progress.

      Dec 05, 2013 09:58
  2. Howard Robinson

    Hi Bruce, this is correct although you can probably drop the word "also" since the status values are now different. 

    Dec 19, 2013 09:46