Jira
Turn a report into a Jira issue with the project's own fields.
Turns a report into a Jira issue in your own project, with the fields Jira actually asks for.
Connect it
- Settings → Integrations → Jira.
- Enter your Jira site URL (
your-domain.atlassian.net), your Atlassian account email, and an API token — create one at id.atlassian.com/manage-profile/security/api-tokens. - Test connection.
- Pick a default Project and Issue type. The issue type list is scoped to the project you picked — Jira's own available types differ per project, so this only shows what that project actually has. If a project has a type named "Bug," it's picked by default.
Filing
Create a → Jira issue, from the capture editor or a filed report. The created issue carries:
- Title and description, with severity/priority/environment and the evidence links
- The screenshot or recording thumbnail
- Only the fields Jira's own create-metadata says the chosen project and issue type actually require — a project with unusual mandatory custom fields won't silently fail because BugCapture guessed wrong about what's needed.
The report gets a Jira reference (the issue key, like PROJ-142) linking straight to it.
One site per workspace
BugCapture connects to one Jira site per person. If your team runs multiple Jira sites, everyone files to the same one that's configured — there's no per-bug site switcher today.