Enhance your incident management process with Incident Tasks by assigning and tracking ad-hoc tasks directly from Slack. Teams can rapidly create tasks ad-hoc as an incident evolves, or they can predefine tasks through Incident Workflows.

📘

Availability

Incident Tasks are included with our Enterprise Incident Management package. Please contact our Sales Team to upgrade to a plan with Incident Tasks.

🚧

Required User Permissions

Incident Tasks' permissions match the associated incident's permissions. Incident Tasks can be assigned to users who have been added as a Responder or are assigned to the incident.

Users with a Responder role or higher can create and update Incident Tasks.

Create Incident Tasks

There are two ways to create Incident Tasks:

• Create an Ad-Hoc Task in Slack or Microsoft Teams
• Create a Task in Incident Workflows

Create an Ad-Hoc Task in Slack or Microsoft Teams

Ad-hoc tasks provide a quick and easy way for responders to capture and assign work while actively responding to an incident.

Create Tasks in Slack

As a prerequisite, please make sure you have configured the Slack integration. To create an ad-hoc task in Slack:

1. On an incident's card, click the More actions dropdown and select Add Task.
2. Enter the following information:
   1. Task Name
   2. Task Description (optional)
   3. Status: SelectTo Do, In Progress, Skipped, or Done.
   4. Assign to: Select Unassigned or one of any users associated with the incident. The list of eligible assignees consists of the user(s) currently assigned to the incident and any Responderswho have been added to the incident.

📘

Slack Integration

Please read Slack Integration Guide | PagerDuty for more information about configuring the integration with Slack.

Create Tasks in Microsoft Teams

As a prerequisite, please make sure you have configured the Microsoft Teams integration. To create an ad-hoc task in Microsoft Teams:

1. On an incident's card, click the additional actions menu button and select Add Task.
2. Enter the following information:
   1. Task Name
   2. Task Description (optional)
   3. Status: SelectTo Do, In Progress, Skipped, or Done.
   4. Assign to: Select Unassigned or search for any PagerDuty user you wish to assign this task to.

Create a Task in Incident Workflows

Pre-defined tasks in Incident Workflows allow responders to add structure to response processes and capture steps that need to be completed for certain types of incidents. As an example, you might add a task to ensure an incident's priority gets set.

In the PagerDuty web app:

1. Navigate to Automation Incident Workflows.
2. Select an existing workflow from the list, or click New Workflow, enter the required information and click Create.
3. In the Actions section, click Add Action, and select Create a Task.
4. Enter a Task name and optionally update the Status, Assignee and Details.

5. When you're finished entering the task information, click Add Action.
6. Click Save.

Additional Incident Task Actions

In addition to creating Incident Tasks in Incident Workflows, you can also use Incident Workflows to automate tasks' other properties. While configuring an Incident Workflow, the following actions, in addition to Create a Task, are available:

• Update Task Assignee
• Update Task Details
• Update Task Name
• Update Task Status

In order to update an Incident Task, you'll need to enter its Task ID. Please read Action-Specific Field References for more information about how to retrieve a value from an Incident Workflow action.

Using Incident Tasks

After you've created an Incident Task, you can view, edit and update them in Slack:

1. On the incident card, click the More actions dropdown and select View Tasks. This will open a modal window in Slack.
2. Use the Filter by dropdown to display your desired task(s).
3. Make your required changes to the assignee and/or task status.
4. When you're finished, click Close.

FAQ

How many tasks can an incident have?

Are task assignees notified when a task is created, assigned or updated?

Are Incident Tasks available in other parts of PagerDuty besides Slack and Incident Workflows?