Jira integration
Every report becomes a Jira issue. A done status resolves it.
- Category
- Issue tracking
- Set up by
- An Owner or Admin
- Status back
- Checked every 10 minutes
- Plans
- Included on all plans
What lands in Jira. One report, as an issue.
How it works. Reports in, status back.
Your project, your type
Reports land in the Jira project and issue type you choose.
The summary, added later
The AI summary lands in the issue description when it’s ready.
Screenshots attached
Added to the issue as files, with a link back to the report.
Status every 10 minutes
Rebase checks Jira every 10 minutes. Done resolves, moving it back reopens.
No duplicates
A repeat of an open report adds a comment to the original issue.
Your fields
Set labels and other fields for every issue under Defaults for new issues.
Set up in minutes. Jira in three steps.
01Open Settings, Trackers, Jira
An Owner or Admin sets this up.
02Allow Rebase
Sign in to Atlassian and allow Rebase.
03Choose the site, project and issue type
New reports become issues there.
Every integration on every plan, from $69 a month.
See pricingQuestions, answered.
Rebase checks Jira every 10 minutes. When an issue reaches a done status, its report resolves at the next check.
GitHub
Linear
Asana
Slack
Description
What the customer wrote
Where it happened
Steps before it
Console
TypeError: Cannot read properties of undefined at applyCoupon (cart.js:48)Network
Summary
The coupon request fails with a 500, then checkout reads a total that was never set.
View the report in Rebase