Jira

Structured issues in the right Jira Cloud project — status syncs back via scheduled polling.

Every ticket can become a structured Jira issue in the right project — screenshot attached natively, triage in the description, status kept in sync with your workflow.

Connect

1. In the widget, open Settings → Integrations → Jira.
2. Authorize via OAuth (Jira Cloud).
3. Pick the site, project and issue type new issues should use.

What a ticket becomes

A proper Jira issue, formatted the way Jira expects:

• The screenshot attached natively to the issue.
• The AI triage — summary, severity, repro steps, type — in the description.
• A rebase label plus the AI's classification.
• A link back to the full Rebase report.
• The suspected source location when available — see Source attribution.

Auto-create is a per-integration toggle; creation runs as a queued job with retries. You can also push any ticket manually from its thread.

Status, both ways — via polling

Resolve the issue in Jira and the Rebase ticket closes; resolve in Rebase and the Jira issue transitions.

Field mapping

Map Rebase priority and status into Jira's fields and workflow values — your taxonomy, your workflow states. Configure it from the integration's settings in the widget.

The badge

Tickets linked to Jira show their key — ACME-77 — as a badge in the widget (owners and team only) that jumps straight to the issue.