Overview
Action items track specific work during incident handling, such as “scale up the database connection pool” or “roll back the latest release”. Manage them in the Actions card on the right of the incident overview page. Each item has a title, a description, and one or more assignees. You can convert an action item into a follow-up, which then enters the post-mortem process. Follow-ups use the same fields and statuses as action items. Action items cover handling; follow-ups cover improvement work after the incident ends. You can create a follow-up directly on a closed incident without a post-mortem report. You can also maintain it in the report’s To-dos block; see Converting to follow-ups and linking to post-mortems.Overview panel
The right side of the incident overview page shows two cards, Actions and Follow-ups, whose editable phases are complementary:
The card that is not editable is read-only and shows existing items only. The editable card comes first.
Both cards use the same inline operations (edit, delete, complete, mark as won’t do). The sections below use action items as the example; the same operations apply to follow-ups.
Creating and editing action items
Create
In the Actions card on the incident overview page, click Add an action (or Add if the card has items). Then fill in these fields:
Once created, the action item appears in the card and the incident timeline records an “action created” event. Members assigned as assignees receive a personal notification prompting them to follow through (sent through email and in-app push by default; you can adjust notification channels in Personal Settings).
Assigning to AI SRE
The assignee picker pins AI SRE above the member list, separated from it by a divider. Search never filters it out, so it stays in the results whatever you type. Selecting it hands the item to the account’s AI SRE, and you can keep member assignees alongside it. Action items and follow-ups share the same create/edit dialog, so the field behaves the same for both.- The card shows the assignment as an AI SRE avatar next to the member avatars (up to 2 avatars, with the rest collapsed into
+N) - Hovering the AI SRE avatar opens a hover card that names the member whose identity and permissions the AI SRE runs with, and offers Continue conversation, which opens the session behind this run in the AI SRE panel
- When the run came from an IM session, the hover card only says IM sessions can’t be viewed on the web yet and offers no entry point
- Opening the session requires AI SRE to be enabled for the account and AI SRE chat permission for you; personal sessions (visible only to their creator) and expired sessions can’t be continued
- On the incident timeline, this work item’s record lists the assignees with a joint signature (for example, “John and AI SRE”)
flashduty incident work-item-list --assignee-type ai_sre in the CLI.
Edit and delete
- Members with incident update permission can click the item title, or use Edit in the More menu, to change the title, description, or assignees
- Newly added assignees also receive a personal notification; removing an assignee does not trigger a notification
- Delete in the More menu requires confirmation; deletion cannot be undone
Status transitions
Manage each action item’s status with its checkbox and the More menu:
The More menu also provides Mark as completed and Cancel completion shortcuts. Status changes are likewise recorded on the incident timeline.
Converting to follow-ups and linking to post-mortems
Follow-ups belong to an incident that has ended. The system converts unfinished action items automatically when the incident closes, and you can keep adding follow-ups afterwards:- Automatic conversion on close: When an incident closes, Flashduty converts all its unfinished action items into follow-ups at once. It writes one timeline record: converted N unfinished actions to follow-ups: title, title…. Completed and won’t-do action items stay as read-only action items
- Automatic post-mortem linking: If the incident has a post-mortem report, Flashduty links new or converted follow-ups to it. Otherwise, follow-ups stay unlinked until someone creates a report, and then Flashduty links them all
- Working in the post-mortem report: You can also edit, complete, or delete linked follow-ups in the report’s To-dos block. The incident timeline records these operations
Permission model
Access to action items and follow-ups follows these rules:
Access to action items also follows the incident’s collaboration space. Only account owners, account admins, and members with access to that space can work on them. Manual incidents without a collaboration space are visible to all account members. This matches the access rules of the incident itself.
Assignees in the table above means account members. A work item assigned to AI SRE is executed by the AI: AI SRE is not an account member, so the member-facing completion permission and personal notification above don’t apply to it (when the same item also has member assignees, those members are notified as usual).
Closed incidents
Once an incident is closed, the Actions card becomes read-only while the Follow-ups card unlocks for editing:- Actions: You can’t create, edit, or delete action items or change their status, and the API rejects creating them too. This card usually holds only completed and won’t-do items
- Follow-ups: You can add, edit, complete, or delete them directly
- To keep an item as an action item, mark it Completed or Won’t do before closing; otherwise, closing converts it into a follow-up
Further reading
- Search and View Incidents: learn about action-item and follow-up events on the timeline
- Create and Edit Post-Mortem Reports: use to-dos in post-mortem reports
- Personal Settings: configure collaboration notifications such as work-item assignment