Integration · Jira
File Jira Tickets With Session Evidence Attached
Every Jira ticket from Relyv ships with the replay link, console logs, network HAR, and reproduction steps. Drop the dev-cycle question "can you reproduce?".
What you get
Replay-attached tickets
Every Jira ticket from Relyv has the replay link, full console + network logs, and AI-generated repro steps in the description. Devs reproduce on first try.
Custom field mapping
Map Relyv metadata to your Jira custom fields — severity, page path, customer tier, AI confidence score. Build dashboards in Jira directly off the data.
JQL-friendly tags
Auto-applied labels follow your team's convention. Filter Jira queries by `relyv-ai-summary-confidence > 0.8` if that's how you triage.
Cloud + Data Center
Atlassian Cloud and Jira Data Center (8.0+) are both supported. Self-hosted teams: we never proxy your tickets through us — direct API calls only.
Setup in four steps
- 1
Connect Jira
Atlassian OAuth for Cloud, API token for Data Center. Workspace admin connects once; the rest of the team uses it without further setup.
- 2
Map projects + custom fields
Choose which Jira projects receive Relyv tickets. Optionally map Relyv metadata (severity, page, AI confidence) to your custom fields.
- 3
Trigger from a session
Click "Open in Jira" from any session. Title, description, priority, and labels are pre-filled — edit before submit if you want.
- 4
Ticket lands with evidence
The ticket appears in your Jira inbox, evidence attached. Jira automation rules can take over from there. Two-way sync mirrors state back to Relyv.
Implementation details
Cloud vs Data Center: what's different
Cloud uses Atlassian OAuth 2.0 with workspace-scoped tokens. Data Center uses API tokens you generate in Jira admin. Both support the same feature set — custom fields, automation, two-way sync. Self-hosted Jira tickets never transit through Relyv's servers; we make direct HTTPS calls from the user's browser.
Custom fields and automation
Any Jira custom field can be a target. Common mappings: Severity → Priority, Page Path → Component, AI confidence → custom number field, Customer Tier → custom select. Once values are in Jira, your existing automation rules (auto-assign, SLA timers) work as-is.
Permissions
OAuth scopes: read project metadata, create issues, read issue state for two-way sync. We never request access to repositories, billing, or admin functions. Tokens rotate automatically; revoking from Jira admin cuts access in under a minute.
Frequently asked
Does this work with Jira Cloud Free / Standard / Premium / Enterprise?
All Jira Cloud plans are supported. Premium / Enterprise teams can use advanced features like sandbox testing — Relyv supports separate Jira sandboxes for dev environments.
Can I use Jira Service Management instead of Software?
Yes. JSM projects are first-class destinations. Customer-impacting bugs from Relyv can be filed directly as JSM service requests with SLA timers attached.
How does Jira automation interact with Relyv?
Once the ticket exists in Jira, Jira owns it. Relyv only writes the initial ticket and reads back state changes for two-way sync. Your existing automation rules run untouched.
What permissions does Relyv need?
Read project metadata, create issues, read issue state for two-way sync. No code, repo, or member-data access. Permissions are scoped to the projects you map; ones you don't map are invisible to Relyv.
Ready to wire up Jira?
Every Jira ticket from Relyv ships with the replay link, console logs, network HAR, and reproduction steps. Drop the dev-cycle question "can you reproduce?".