Jira integration

Configure Jira Cloud issue delivery as properly formatted issues. Every new report is dispatched automatically, just after it is stored.

What you need

A Jira Cloud site, the project key you want issues created in, an issue type that exists in that project, the Atlassian account email, and an API token for that account.

BugLoop authenticates with Basic auth over HTTPS using the email and API token, which is the documented mechanism for Jira Cloud REST APIs.

Connecting

Open Integrations → Jira. Enter your site URL (https://yourcompany.atlassian.net), the project key, the issue type name, and the account email. Paste the API token and save.

Test connection performs a real authenticated read of the Jira project and reports the project name back, confirming both the credential and the project key in one step.

Formatting

Jira Cloud's v3 API takes rich text as Atlassian Document Format rather than Markdown, so BugLoop converts the report into ADF: headings for each section, bulleted lists for context and custom fields, bold labels. The ticket reads the same as the GitHub issue.

Issue type gotchas

The issue type name must exist in the target project and must be spelled exactly — "Task", "Bug", "Story". If your Jira admin renamed it, use the renamed value. A mismatch shows up immediately in Test connection rather than silently at 2am.