Actions and follow-ups in step with Linear and Jira

An incident's actions and follow-ups can now live in Linear or Jira too. Change an item's title, status or assignee in Firefight and its issue follows, and a change made to the issue comes back to the item. Set it up in the Issue tracking card on the Workspace settings screen. See Issue tracking.

When an item gets an issue. Choose Never, Only when someone asks, Always for follow-ups or Always for actions and follow-ups. It applies however the item was added, from Slack, the dashboard, the API, an agent over MCP or Halon.

Create issue. Unless the setting is Never, an item without an issue offers Create issue on the incident page and on its message in the incident channel. Agents use create_action_item_issue. The issue carries the item's title, the incident's identifier and a link back to the incident.

Both ways. Picking up, handing over, completing, reopening and renaming an item move the issue to match. Completing, reopening, reassigning or renaming the issue in the tracker does the same to the item, and the channel hears when it is done. People are matched by email.

More you can do with an item. Rename, reopen and unassign are now in each item's menu on the incident page, on its message in Slack, and over the API and MCP (rename_action_item, reopen_action_item, unassign_action_item).

Recorded. Every change made either way is in Activity under Gateway, with the source Issue sync.