Slack
Link a Slack channel, or one thread in a channel like #incidents, to an incident, and the messages land on its timeline with their original times and authors. Linking late is fine: what was already said is pulled in when you link.
How it reaches Jira
Slack cannot talk to an app inside your Jira site directly, so messages pass through the Afterbrief Relay, a small service we host in the EU. It forwards each message to your site through one signed endpoint and keeps no copy of it. The Afterbrief app itself never calls out of Atlassian.
What the relay stores:
- your site's address, the app's inbound address on it and the shared secret it signs requests with (encrypted at rest);
- the Slack workspace's id and its installation (the bot token and the id of the person who installed it), encrypted at rest;
- which channel or thread is linked to which incident, the channel's name, and whether a channel is a hub.
Messages are held in memory for a few seconds while they are batched, then forwarded and dropped; after ten minutes of failed delivery they are dropped anyway. Its logs carry counts and ids, never message text.
Set it up (once per Slack workspace)
A Jira admin opens Jira settings → Apps → Afterbrief defaults → Chat capture:
- Store a shared secret. Generate one and store it. The relay signs every request to your site with it.
- Add Afterbrief to Slack from relay.afterbrief.pro, then paste this site's inbound URL and the secret on the relay's connect page. The relay checks them against your site before it saves anything.
- Turn on message capture (optional). Without it, only commands and the message shortcut reach the timeline; with it, everything said in a linked channel or thread does.
An admin can also limit which spaces chat may write into.
Commands
Chat only acts on work items that are already incidents: declare in Jira first, or turn on automatic declaring.
| In Slack | What happens |
|---|---|
/incident link INC-123 |
Links this channel to the incident and pulls in the last 24 hours. Add since 2h, since 09:15 or since all (30 days) to change how far back. Public channels are joined automatically; for a private channel, /invite @Afterbrief first. |
/incident note <text> · /incident key <text> |
Adds a note, or a key moment. Start with a time like 14:05 to backdate it (UTC). |
/incident mitigated · /incident resolved |
Marks the incident in Jira. |
/incident unlink |
Stops capturing this channel. |
@Afterbrief link INC-123 in a thread |
Links just that thread, for teams that run every incident as a thread in one channel. |
/incident mode hub · /incident mode channel |
Makes this channel a hub, where each incident is its own thread, or back to one incident per channel. Also @Afterbrief mode hub. |
| Add to incident timeline (message shortcut) | Saves one message to the linked incident, with or without capture on. |
A 📌 reaction on a captured message makes it a key moment. Bot alerts are captured too: they are often the best evidence of when the incident was detected.