Why professional teams choose JIRA Software and Bitbucket

In this webinar we'll look at integrating JIRA Software with Bitbucket to optimize your development workflow.


Issue trackers, like JIRA Software, and Git repository hosts, like Bitbucket, are vital to your development workflow. However, keeping them in-sync can be painstaking, error-prone, and a hit to developer productivity. 

In this webinar we'll look at integrating JIRA Software with Bitbucket to optimize your development workflow.

Topics we'll cover include:

  • Linking commits, branches, and pull requests to their corresponding JIRA Software issues (and vice-versa), for more effective status tracking and powerful forensic debugging.
  • Automatically transitioning JIRA Software issues when your code is committed, reviewed, merged, or deployed. This keeps your issues up to date with your repository, without your developers having to make the effort (or even remember) to update JIRA Software.
  • Using the JIRA Software project releases page to reconcile upcoming release versions, and resolve issues with unreviewed code, broken builds, or unmerged branches.
  • Generating custom reports by querying the code and build artifacts related to your issues using JIRA Software's powerful JQL search.


Q1. How do you run tests with JIRA and Bitbucket branches?

A1. Typically when a developer pushes to a branch or creates a new branch, their continuous integration server (whether it's bamboo or something else) will be set up to monitor when that branch is updated. Bitbucket server and cloud can be configured to send a web hook notification when a branch is updated and trigger the continuous integration build.

Q2. If I am a current JIRA user, can I import my existing Git repositories into Bitbucket?

A2. Yes, at the end of the day Git is a really nice audible format. It doesn’t really matter what you are currently using to host your Git repositories, importing it into bitbucket is really just as simple as doing a clone with the - -mirror option to get a full copy of your repository from your existing Git host, and then doing a Git push - -all, into Bitbucket to create that copy. Read more here.

Bitbucket also has specialized importers for a few repository hosting solutions, so you can put your credentials or the location of your repository into Bitbucket and it will pull it down for you.

Q3. Does JIRA support deleting feature branches in Bitbucket Server after they are merged?

A3. Yes. Regardless of whether you are using Bitbucket server or cloud, when you hit the merge button on a pull request, it will give you the option of deleting the branch after the merge has taken place. If you don’t delete it on the spot, you can later delete them locally, or you can go in and delete them via the server and cloud user interface.

Q4. Can you customize which JIRA issue state to transition to when a branch is updated in Bitbucket?

A4. The JIRA workflow triggers are really flexible so you can bind them to any transition you have in your existing workflow. You can trigger any workflow action based off any repository action; it really depends on what you want to do in your workflow. The example workflows I show in the webinar are a few examples of what’s possible. So yes, absolutely!

Q5. Is there a way to merge or lock binary files with Bitbucket?

A5. Essentially whatever Git can do you should be able to do in Bitbucket. Specifically that means locking is not an option.

Q6. How does Bitbucket associate a pull request with an issue?

A6. A pull request will be associated with an issue if it contains a commit that references the issue key. For example, if the source branch for the pull request contains a commit with the issue key in it, if the pull request contains an issue key in its title, or if the issue key is in the name of the source branch, it will be as. If you click on the "create branch" link from the JIRA issue page, the issue key will pull into the branch and will make sure your pull requests are bound correctly to your JIRA issues. 

Q7. How does Bitbucket handle merge conflicts?

A7. You’ll see a merge conflict in the Bitbucket user interface if you create a pull request where you change a file that has been modified in different ways on both the source branch and the target branch pull request. As part of the pull request process, this will render as a nice diff showing the changes that you’ve made, or that have occurred on both branches. If there is a conflict it will display little conflict markers highlighted in bright orange around the lines that are currently conflicted. You can’t actually resolve those conflicts via the pull request user interface, but you can pull down that branch and then resolve the conflicts locally. You will get some commands displayed inside the Bitbucket UI on how to do that, and then you can push a new commit that has those conflicts resolved. Then, you will be able to merge the pull request via the user interface.

Q8. For the building process, do you need Bamboo or can you use another third party builder like Jenkins?

A8. JIRA Software and Bitbucket does integrate and will work with third party builders like Jenkins. However, the deepest integrations are with Bamboo and using JIRA Software and Bitbucket with Bamboo is recommended to maximize most of the benefits seen in this webinar.

Q9. How is the branch type prefix configured in JIRA, so that the automatically generated branch names will include it?

A9. Any bug will map to a bug fix and anything else will map to a feature.

Q10. Is Bitbucket cloud going to get all the features of Bitbucket Server?

A10. Bitbucket Cloud and Bitbucket Server began with different technical architectures and different feature roadmaps. Over the past two years, much progress has been made in bringing conceptual and functional parity to the products, and we are working to continue this feature parity.


Tim Pettersen

Developer Advocate, Atlassian

Tim served a few years as a developer on the JIRA, FishEye/Crucible and Stash teams. In early 2013 Tim switched to developer advocacy to spend some time traveling the world and meeting other like-minded developers. These days he speaks and blogs about developer workflows, Git, continuous integration/deployment and Atlassian's developer tools: especially Stash. He regularly tweets about these things and other Atlassian arcana as @kannonboy. 


Want to hear about more webinars like this one? Sign up! We promise not to clutter your inbox!