> ## Documentation Index
> Fetch the complete documentation index at: https://docs.promarshal.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Action items

# Action Items Capture

ProMarshal monitors your Jira comments in real time and automatically extracts action items — things like follow-ups, handoffs, and coordination tasks that get buried in comment threads and forgotten.

***

## How detection works

When a comment is added or updated on a Jira issue, ProMarshal processes it through two stages:

**Stage 1 — Keyword filter**

The comment is scanned for phrases that signal a follow-up action:

* `ask [person] to`
* `assign`, `owner is`
* `follow up with`, `remind`
* `coordinate with`, `loop in`
* `handoff`, `nudge`, `chase`, `check with`

Comments that only describe a status update (`done`, `completed`, `fixed`, `deployed`) are filtered out at this stage and not processed further.

**Stage 2 — LLM classification**

Comments that pass the keyword filter are sent to an LLM (OpenAI) for classification. The model determines whether the comment implies an external follow-up that should be tracked as an action item. Only comments classified with confidence above **0.75** are captured.

This two-stage approach avoids capturing routine status updates while catching coordination tasks that a keyword filter alone would miss.

***

## What gets captured

For each detected action item, ProMarshal extracts and stores:

| Field          | Description                                          |
| -------------- | ---------------------------------------------------- |
| Title          | A clean, rewritten summary of the action item        |
| Assignee       | The person mentioned as responsible, if identifiable |
| Created by     | The Jira user who wrote the comment                  |
| Source         | The Jira issue key the comment was on                |
| Status         | `open` on creation                                   |
| Due date       | Inferred from comment context if mentioned           |
| Follow-up flag | Set if the item needs escalation                     |

Raw message content is not stored. Only the extracted fields above are saved.

***

## Where action items appear

Captured items appear in:

* **ProMarshal dashboard** — Pulse → Action Items
* **Action Agent digest** — sent via Slack to the project owner on a schedule
* **Slash command** — `/promarshal actionitem list` in Slack

***

## Deduplication

ProMarshal will not create a duplicate action item from the same comment within a **7-day window**. If the same follow-up is mentioned again in a different comment, it is treated as a new item after the window expires.

***

## Follow-up escalation

If an action item is marked as needing follow-up, ProMarshal escalates it:

* Reminds the assigned owner after **48 hours**
* Notifies the project manager after **4 hours** if the item is unacknowledged

***

## Requirements

* Jira connected to the project (webhooks are registered automatically on connection)
* Action Items capture is active as long as Jira is connected — no additional setup required

***

## Limitations

* Captures from Jira comments only. Slack message capture is not currently supported.
* Assignee detection works best when the comment explicitly names a person. Implied references may not be extracted.


Built with [Mintlify](https://mintlify.com).