JIRA Integration
Tag builds and tests with JIRA tickets, view live issue status, and link directly to triage notes.
BuildButler integrates with JIRA to connect your CI failures directly to the tickets tracking them. Once configured, JIRA ticket references become clickable links throughout the UI, and BuildButler pulls live issue status badges so you can see at a glance whether a failure is already tracked and being worked on.
To enable JIRA integration, configure your credentials in Settings → JIRA Integration.
Tagging builds and tests with JIRA tickets
You can tag a build or individual test failure with a JIRA ticket reference directly from the triage panel. References follow the format [PROJECT-123].
Tagging a build
- Open a build from the Build Results page
- Click Triage on the build
- In the triage notes, type a JIRA reference such as
[AB-123] - Save the note — the reference becomes a clickable link to the JIRA issue
Tagging a test failure
- Open a test from Test Results or Test History
- Click Triage on the failing test
- Add a JIRA reference in the triage note (e.g.
[AB-456]) - The reference links directly to the issue in your JIRA instance
Live issue status badges
When JIRA email and API token are configured, BuildButler fetches the current status of each referenced issue and displays it as a badge next to the ticket link.
| Badge | Meaning |
|---|---|
| To Do | Issue is logged but not yet started |
| In Progress | Issue is actively being worked on |
| In Review | Issue is in code review |
| Done | Issue is resolved |
Status badges update automatically so you don't need to manually check JIRA to know whether a failure is being addressed.
Triage workflow with JIRA
The combination of triage notes and live JIRA status creates a complete workflow:
- New failure — triage the build or test, create a JIRA ticket, tag it in the note
- Tracking — the JIRA badge shows In Progress next to the failure across all dashboards
- Resolved — when the ticket is closed, the badge updates to Done, giving the team confidence the fix is in
This makes it easy to distinguish known, tracked failures from new regressions without leaving BuildButler.