> For the complete documentation index, see [llms.txt](https://docs.pagerly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pagerly.io/incident-response/action-items.md).

# Action Items

Action items are the follow-up tasks that come out of an incident — "add alerting for the connection pool", "write a runbook", "fix the retry logic". Pagerly lets you capture them at any point (during the incident or in the postmortem), assign an owner and priority, push them to your issue tracker, and chases the ones that go overdue.

## Creating action items

You can create action items from three places — during an active incident **or** after resolution:

* **From Slack** — open the incident message's action menu (**⋯**) and choose **✅ Add Action Item**. A form opens for the title, details, assignee and due date.
* **From the dashboard** — on the incident page, open the **Action Items** tab and click **+ Add action item**.
* **From the postmortem** — click **Add as action item** on any AI-suggested follow-up.
* **Via MCP / AI** — see [MCP tools](#mcp-tools) below.

## Fields

| Field           | Notes                                            |
| --------------- | ------------------------------------------------ |
| **Title**       | What needs to be done (required)                 |
| **Description** | Optional details                                 |
| **Assignee**    | The owner, by email / Slack user                 |
| **Due date**    | When it's due                                    |
| **Priority**    | `P1` (highest) → `P4`                            |
| **Status**      | `Open` → `In Progress` → `Done`                  |
| **Team**        | Inherited automatically from the linked incident |

## Assigning & updating

Assign or reassign an owner, change the priority or status, and edit details from either Slack (at creation) or the dashboard (any time). Priorities are shown as colour-coded badges (P1 red → P4 grey) everywhere action items appear.

## Sync to Jira / Linear

Push an action item to your issue tracker as a standalone task. Click **Sync** on the action item; Pagerly creates the issue and stores a link back to it.

* **Jira** — set the destination **project key** in the incident settings.
* **Linear** — set the destination **team id** in the incident settings (or Pagerly uses your first Linear team).

If no tracker is configured, the Sync action tells you so and does nothing — it fails safe.

## The Action Items page

A dedicated **Action Items** page (under **Incidents & Paging**) lists every action item across all incidents, so open follow-ups are never buried inside individual incidents. Filter by:

* **Status** (Open / In Progress / Done)
* **Priority** (P1–P4)
* **Team**
* **Incident**

Each row links back to its incident, and status can be changed inline.

## Overdue reminders

Pagerly runs a daily check and **DMs the assignee** about any action item that's past its due date and not yet Done, with a **Mark done** button right in the message. This is what keeps postmortem follow-ups from quietly dying in a list.

## MCP tools

If you use Pagerly's [Remote MCP Server](/sre-ai-agent/remote-mcp-server.md), action items are fully available to AI clients:

* `pagerly_create_action_item` — create an item, optionally linked to an incident and assigned to someone
* `pagerly_list_action_items` — list/filter by incident, assignee, status or open-only
* `pagerly_update_action_item` — change status, reassign, or edit title/description/due date

This lets you say things like *"create an action item to add DB alerting, assign it to priya@, due Friday"* or *"what open action items does the payments team have?"*