🔗 New! Official Bitrise for Jira app

Bitrise for Jira is a new, free app available from the Atlassian Marketplace that brings info about your Bitrise builds directly into your Jira tickets. It’s available on all Bitrise plans.

:persevering_face: The problem

Jira is the one place developers, QA, managers, and execs all agree to check for a ticket’s status, but until now, it had no idea what Bitrise was doing.

Developers had to flip over to Bitrise or GitHub just to confirm their own build passed. QA, managers, and execs usually couldn’t check at all, since they don’t have Bitrise or GitHub access, so they’d interrupt a developer to ask instead.

And once a ticket closed, there was no record of which builds had actually touched it, making it harder to trace a bug back to the build that introduced it.

:wrapped_gift: The solution: a dedicated Bitrise-Jira integration

:purple_heart: A dedicated Bitrise section on every ticket

If the Jira issue-key is present in your branch, commit, or PR title you’ll see a new Bitrise section on the Jira ticket which shows the live build status. Pipeline builds can be expanded to show the status of each individual child build.

:link: Click through to the build

From the ticket, jump straight to the build’s full logs and status in Bitrise. No searching for the right build in a long list.

:stop_sign: Abort a running build from Jira

If a build is going to fail or was triggered by mistake, abort it directly from the ticket. No need to switch tools first.

The build information also appears in the generic Development section provided by Jira:

:rocket: How to get started

You just need to ask your Jira admin to install Bitrise for Jira from the Atlassian Marketplace.

Once connected, there’s nothing else to configure. Issue-key detection works automatically as long as a Jira issue key appears in your branch name, commit message, or PR title.

Find out more in our documentation.

:information_source: Important notes

  • This release supports Jira Cloud only. Jira Data Center and Server aren’t supported yet.

  • Issue-key detection depends on the key showing up in your branch, commit, or PR title. If none of those carry a recognisable key, that build simply won’t link to a ticket.

:crystal_ball: What’s next?

Deployment status, mobile-specific pipeline stages, and ticket automation aren’t in this release, but they’re on the roadmap.

Happy building! :waving_hand: