Skip to main content

Issue Trackers

Issue-tracker integrations let AI Expedite read tickets as roadmap candidates, push roadmap items back as tickets, and surface tracker activity in your Inbox. Three trackers are supported today — Jira, Linear, and Confluence — each connected via OAuth from Settings → Integrations.

📷 Screenshot: Issue-tracker rows on Settings → Integrations.

What they share​

All three trackers follow the same pattern:

  • OAuth handshake for setup, with workspace-scoped storage of refresh tokens.
  • Inbound webhooks that route tracker events into Inbox under the Integrations category.
  • Optional scope upgrade — connect read-only first (just to surface tickets) or read+write (so agents can update tickets too).

Removing any of them stops the workspace reading or writing through that tracker; existing data already pulled into Roadmap or workspace documents stays intact.

Jira​

Two-way sync with Jira issues across your connected projects.

  • Connect from: Settings → Integrations → Jira.
  • Powers:
    • Roadmap → Backlog candidates pulled from Jira issues, with the AI prioritizer ranking them alongside other signals.
    • Status sync — moving a Roadmap card from In Progress to Review updates the linked Jira ticket's status, and vice versa.
    • Inbox notifications — assignment, comment, status-change, and mention events arrive as Inbox notifications under the Integrations category.
  • Per-project scoping: pick which Jira projects expose to the workspace. Tickets outside that selection are invisible.

Linear​

Same shape as Jira — bidirectional ticket sync, webhook-driven notifications.

  • Connect from: Settings → Integrations → Linear.
  • Powers: identical to Jira's surface — Roadmap candidate pulls, status sync, Inbox notifications.
  • Project / team scoping: choose which Linear teams' issues are visible.

When both Jira and Linear are connected (rare but supported), the Roadmap merges candidates from both with the source label visible on each card.

Confluence​

Read-only by default — agents can read Confluence pages as context when implementing a feature or drafting documentation. An optional write scope lets agents post a release note or update a runbook.

  • Connect from: Settings → Integrations → Confluence.
  • Powers:
    • Read-as-context — pin a Confluence page to a chat or attach it as a reference inside an agent step, and the page content gets pulled in at run time.
    • Write-back (with extra scope) — agents can update a Confluence page when authoring or revising documentation. Write scope is opt-in; without it, agents can't modify pages even if they wanted to.
  • Space scoping: limit which Confluence spaces the workspace can access.

Reconnecting​

When any of these tokens lapse, the affected Roadmap / chat / agent surfaces show a Reconnect action on the relevant card or message; Settings → Integrations also surfaces the same action on the integration's row. Reconnecting walks the OAuth flow again and the workspace resumes where it left off.