// Integrations
Trackers & sync
How tickets become issues in GitHub, Linear, Jira and Asana — and how status flows back to Rebase.
Tickets land in the tracker you already use — GitHub, Linear, Jira or Asana — as structured issues with the full context attached. No second inbox, no copy-paste. Slack gets the notifications.
Connecting a tracker
Every integration is connected from the widget: Settings → Integrations, pick the tracker, authorize, choose the destination. All four are first-class:
| Tracker | Connection | Destination picker |
|---|---|---|
| GitHub | GitHub App | Repository |
| Linear | OAuth | Team + intake state |
| Jira | OAuth (Jira Cloud) | Site + project + issue type |
| Asana | OAuth | Workspace + project |
OAuth and App tokens are stored encrypted and refreshed before they expire. Disconnect any time — existing issue links are preserved.
Auto-create and manual push
New tickets can draft a tracker issue immediately — title, description, AI triage, screenshot — without anyone touching the tracker. It's a toggle per integration, and issue creation runs as a queued job that retries transient failures.
Prefer to file by hand? Every ticket thread has a push to tracker control that creates the issue on demand in any connected tracker.
What lands in the issue
- The screenshot, inside the issue itself — uploaded natively on Linear, Jira and Asana, inlined on GitHub. Not a link back to another tool.
- The AI triage — summary, severity, repro steps and type, formatted into the issue body so the assignee starts with context.
- Smart labels — issues are labelled
rebase, plus the AI's classification as your tracker's conventional label (bug, enhancement or question on GitHub). - The suspected source location, when available — see Source attribution.
Two-way status sync
Close the issue in GitHub, Linear or Asana and the Rebase ticket resolves — its pin leaves the page. Reopen it and the ticket reopens. Each sync direction is toggleable.
Field mapping
Map Rebase fields like priority and status onto your tracker's own taxonomy — labels on GitHub, fields on Linear and Jira, workflow values on Jira. Field mapping is available on GitHub, Linear and Jira; Asana syncs status but has no field mapping.
Duplicates, cross-referenced
When a ticket is detected as a duplicate, the canonical tracker issue gets a "see also" cross-reference comment, so related reports are visible from the original issue. Duplicates are detected and linked — see AI triage.
Tracker badges in the widget
Tickets show their tracker reference — #142, ENG-142 — as a badge that jumps straight to the issue. Badges are visible to owners and team members only.
Slack
Slack is for notifications rather than issues: paste one incoming webhook and Rebase posts when tickets are filed and resolved. See Slack notifications.