Routing and notifications — Slack, Linear, Jira
Configure where Watari posts updates and where draft tickets land. Includes the Slack channel-invite step and the Jira ADF requirement.
TL;DR
Routing and notifications — Slack, Linear, Jira
Routing destinations are where Watari posts updates and creates secondary tickets. They are distinct from your support tools (Zendesk and Intercom), which feed tickets in. You can wire all three routing destinations or none — they're optional additions that make the pipeline visible to your wider team.
All three integrations are bundled — they never add to your Mapped Bug count.
You don't need Slack, Linear, or Jira to get value from Watari. Draft PRs and RCAs work through GitHub alone. Routing destinations are about team visibility, not pipeline function.
Connecting routing destinations
Connect Slack
In the Watari dashboard, go to Settings → Integrations and click Connect Slack.
You are redirected to the Slack OAuth authorization screen. Sign in with a workspace admin account and click Allow.
You are returned to Watari. Select the channel or channels you want Watari to post into.
Invite the Watari bot to each selected channel. In Slack, open the channel, type /invite @Watari, and confirm. This is a Slack permission model requirement — the bot cannot post to a channel it hasn't been invited to, regardless of the OAuth authorization. The Watari settings page shows an Invite bot button next to each channel to make this one click.
What Watari posts to Slack
- New Mapped Bug — when a bug qualifies, Watari posts a summary with severity, affected feature, and a link to the bug detail page. The message includes a live CI status line that updates in-place as checks run on the draft PR — the channel doesn't flood with per-check noise.
- Cluster-grew alert — when a recurring issue's customer count crosses your configured threshold.
- PR ready for review — when a draft PR is opened, with a link and the auto-assigned reviewer.
- PR merged / PR failed — status update when the PR is closed. If CI fails on a Watari-drafted PR and the verify-loop gives up, a separate
[ATTENTION]message is posted that mentions the assigned reviewers directly — this is designed to break through muted-thread notifications. - RCA published — when the customer-facing RCA goes out. Configurable in Notifications and digest — per-event toggles and daily digest settings.
Channel-gone behavior
If Slack returns a channel error (the channel was archived, the bot was kicked, or the channel was deleted), Watari pauses posting to that channel and marks the integration as errored. A monthly job rechecks errored integrations automatically — if the channel is unarchived or the bot is re-invited, posting resumes without any manual reconnect. You can also trigger a recheck by visiting Settings → Integrations and clicking Recheck.
Connect Linear
In the Watari dashboard, go to Settings → Integrations and click Connect Linear.
You are redirected to the Linear OAuth authorization screen. Authorize access to your workspace.
Select the Linear workspace and team where Watari should create issues.
You are returned to Watari. The connection status shows Connected.
What Watari does with Linear
When a Mapped Bug qualifies, Watari creates a Linear issue in your selected team. The issue includes the extracted bug title, description, severity, repro steps, and a link back to the Watari bug detail page.
Status-change sync is one-way: Watari creates the issue and updates the link. It doesn't read Linear issue statuses back into Watari.
Linear integration is outbound only. Watari doesn't subscribe to inbound Linear webhooks.
Connect Jira
In the Watari dashboard, go to Settings → Integrations and click Connect Jira.
You are redirected to the Atlassian OAuth authorization screen. Sign in with a Jira admin account and authorize access.
Select your Jira site and the project where Watari should create issues.
You are returned to Watari. The connection status shows Connected.
Jira ADF requirement
Jira's API requires issue descriptions to be in Atlassian Document Format (ADF), not Markdown. Watari handles the conversion automatically — the bug description that appears in Jira is formatted as ADF even though you see it as Markdown inside Watari. You may notice minor formatting differences between what appears in Slack or Linear (Markdown) and what appears in Jira (ADF-rendered) — this is expected and not an error.
What Watari does with Jira
When a Mapped Bug qualifies, Watari creates a Story in your configured Jira project. The story includes the bug title, ADF-formatted description, severity mapped to Jira priority, and a link back to the Watari bug detail page.
Jira integration is outbound only. Watari doesn't read Jira issue statuses back.
Disconnecting
To disconnect any routing destination, go to Settings → Integrations, find the integration, and click Disconnect. Watari stops posting immediately. Historical bugs and any issues already created in Linear or Jira remain in those systems — Watari doesn't clean them up on disconnect. See Disconnecting integrations — token revocation and data retention windows for full details on token revocation and data retention.
Next: Webhooks and events — subscriptions, retry behavior, and outbound event surface — the full list of what Watari subscribes to and what it sends out.