The Jira + Bitbucket integration just leveled up

By on October 17, 2017

Back in March 2017, you gained the ability to view your Jira issues from Bitbucket Cloud, making it much easier to stay in sync with your team without leaving Bitbucket. But this didn’t solve having to visit Jira if you wanted to make any updates to an issue. Developer time is money and we don’t want you to waste it by jumping between Bitbucket and Jira to update, comment, or transition issues. That’s why we’re excited to announce that we’ve brought Jira issue editing power to Bitbucket.

Next time you do a peer review on someone’s code in Bitbucket and you need context from Jira, open the issue right from Bitbucket and add comments, attachments, or even transition the issue to done.

So what’s new?

The latest improvements are all about giving you the ability to update Jira issue information from Bitbucket. Now you can…



What’s next

We will continue to invest in making Bitbucket and Jira easier to use together, further speeding your development cycle. Up next, we are focused on the following items.

How to get started

Ensure Bitbucket and Jira Software are connected. 

If you’re already using issue keys in your commit messages today, simply click on the links to enjoy visibility on Jira issues. If you’re not using issue keys in Bitbucket, try adding one to your next commit message. Type out an issue key that exists in one of your Jira projects, for example, “TEST-123” and voilà, you should now be able to click on the issue keys to view it’s details. Read more about using issue keys in Bitbucket here. 

Having trouble? You may need to reconnect your Jira and Bitbucket connection. Visit our troubleshooting page if you run into issues or contact support.

Not using Jira Software and Bitbucket together?

Jira Software is the preferred issue tracker of over 350,000 Bitbucket teams. We did an extensive study amongst our users and found teams who have Jira Software and Bitbucket integrated release 14% more often and close 23% more issues (when compared to teams using just one of those products).

Learn more