# Issue trackers

Connect Jira, Linear, or Monday so a Brizz issue becomes a ticket in the tracker your team already works from.

Brizz creates tickets in three issue trackers — **Jira**, **Linear**, and **Monday** — so a problem Brizz detected becomes a ticket in the tool your team plans work in, without retyping it. GitHub can also be connected, but it has no ticket actions on an issue yet; add a GitHub URL with **Add Link** instead.

## What connecting gets you

- **Create a ticket from a Brizz issue.** The ticket carries the issue's title and description. How much else travels with it varies by provider — Jira and Monday embed session context and a link back, while the Linear body ends with a generic link to Brizz rather than a deep link to the issue.
- **Attach an existing ticket.** If someone already filed it, link the two rather than creating a duplicate.
- **See the link from Brizz.** Linked tickets show as badges on the issue. Jira and Linear links also show the ticket's current status; a Monday link shows the item name only.
- **Automatic status handoff.** Linking a ticket — or adding any external link — moves the Brizz issue to **Tracked**, so your open queue reflects what's actually been picked up. See [Issues](/docs/platform/issues.md) for what the statuses mean.

## Connecting

1. Go to **Settings → Integrations**.
2. Find the tracker's card and click **Connect**.
3. Authorize Brizz in the provider's own consent screen, then return to Brizz.

Jira, Linear, and Monday connect over OAuth. When none of them is connected, the **Add Link** control on an issue also offers to set one up — it takes you to Settings to finish, and doesn't return you to the issue you started from. See [Jira](/docs/integrations/jira.md) for that integration's permission list and project setup.

To disconnect, use the same card and click **Disconnect**. Tickets you already created stay in the tracker; you just stop being able to create new ones, or to read Jira and Linear status from Brizz.

## How to act on it

1. **Connect the tracker your team actually plans in.** The value is that Tracked reflects reality — if the tickets live somewhere your team doesn't look, it doesn't.
2. **Attach rather than create when a ticket exists.** Two tickets for one issue split the discussion and neither shows the whole picture.
3. **Let Tracked do the triage bookkeeping.** Once linked, the issue leaves your untriaged queue automatically; you don't have to remember to change the status.

## Availability

Connecting and disconnecting integrations is an **Organization Admin** action, and it also depends on your plan — a connection attempt on a plan that doesn't include the integration is refused with an upgrade prompt.

## See also

- [Jira](/docs/integrations/jira.md) — the Jira integration in detail, including required permissions.
- [Issues](/docs/platform/issues.md) — what tickets get created from, and what the Tracked status means.
- [Slack](/docs/integrations/slack.md) — notifications rather than ticketing.
- [External links](/docs/instrument/external-links.md) — attach arbitrary links to sessions from your own code.