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.

Routing destinations are where Watari posts updates and creates secondary tickets. They are distinct from your support tools (Zendesk, Intercom, and Freshdesk), 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 Issue 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.

Public channels need no invite (Watari joins the channel you pick automatically. For a private channel, invite the bot first: in Slack, open the channel, type /invite @Watari, and confirm) it then appears in the channel picker. If auto-join fails for any reason, the settings dialog shows an inline invite hint.

Send a test notification. In the Slack configuration dialog, click Send test notification, a sample alert posts to your saved channel within a few seconds, confirming the wiring end-to-end before any real ticket arrives.

What Watari posts to Slack

New Mapped Issue: 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 Issue 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'll be offered two ways to connect.

Continue with Atlassian (recommended) sends you to Atlassian's authorization screen. Sign in with an account that can open your Jira site 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.

If Atlassian says there's no Jira site

Some Atlassian organizations require an admin to approve an app before it can be installed. When that's on, Atlassian still completes the sign-in but grants access to nothing, so Watari reports that no Jira site came back. The same message appears if you signed in with an Atlassian account that isn't a member of your Jira site.

You have three ways forward, all on the Integrations page:

Sign in as a different account. Sign out of Atlassian (or use a private window) and connect again as someone who can open your Jira.
Ask your admin to approve Watari. Watari gives you a ready-to-send message. Your admin approves it under Atlassian Administration → Apps → your site → Connected apps. Atlassian has no way to request this from the consent screen, which is why we hand you the text.
Connect with an API token instead. This works immediately, without waiting for an approval.

Connect with an API token

Choose Use an API token instead in the Connect Jira dialog, then provide:

Jira address: whatever you open Jira at, including a custom domain such as jira.yourcompany.com.
Atlassian account email: the address you sign in to Atlassian with. Watari files issues as this account, so it needs permission to create issues in your target project.
API token: create one at id.atlassian.com → Security → API tokens.

Watari verifies the credentials against Jira before saving, and picks a default project you can change under Configure.

Two things to know. Atlassian API tokens expire (up to a year, and your admin can set a shorter limit), when yours stops working, Watari marks the integration as needing reconnection and notifies your workspace owners rather than failing quietly. And some organizations block API-token creation as well; if yours does, the admin-approval route above is the way in.

Jira Cloud only. Jira Data Center and Jira Server are not supported yet, and Watari will tell you if you point it at one.

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 Issue 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.

Routing and notifications: Slack, Linear, Jira

On this page