Organisations we work with tell us they love using Atlassian tools because the way that they integrate allows them to have traceability through the SDLC - the foundation for The DevOps Loop and end to end ideation to realisation capabilities.
Studies show that organisations that integrate JIRA Software with Bitbucket have fewer status meetings and release an average of 14% faster than teams using a different repository management solution. So HOW do the tools integrate and why does the integration increase velocity and improve productivity?
Atlassian's claim is:
Bitbucket and JIRA Software are seamlessly
integrated, from branch to deployment
Let's have a look at that in a bit more detail and see what it really means.
First off, you can create Bitbucket branches from INSIDE JIRA Software. This helps to give an entire development team context around every branch. JIRA Software automatically populates information for your new branch in Bitbucket and even suggests a branch name based on the issue key. Nice.
Secondly, if you're working in Bitbucket, you can transition issues from there by creating triggers in JIRA software for actions that are occurring in Bitbucket. You can sync pull requests, commits, and branches in Bitbucket to your JIRA Software workflow so that issues will automatically update as you work. Cool, huh?
More About Traceability
It's that traceability as we said that our customers love; the JIRA Software Release Hub talks to Bitbucket to ensure that done code is really done and there are no inconsistencies or launch risks prior to launch day allowing the tracking of the health and status of the next release from day one of development. That's building quality in that supports the devops principle of never knowingly allowing a defect to pass downstream. We had an interesting conversation with a customer last week about this principle whose initial response was that this could be contrary to value driven engineering in that it prioritised perfection over delivering just good enough capability. When we inspected the thinking further though we all agreed that because building quality in is such an important approach, the volume of potential defects that COULD be passed downstream would be minimised to near zero. Recognising the impact, not just of potential outages but also of the build up of the technical debt that keeps so many enterprises in fire-fighting mode is critical.
Here's a summary of the benefits:
- See all the related commits, branches and pull requests in an issue.
- Create Git branches from within JIRA Software
- Transition issues automatically and from within Bitbucket
- See all related branches, commits and pull requests in an issue
- Use issue keys in Bitbucket Server markdown
- See the details for issues in Bitbucket Server
- See issues related to Bitbucket Server commits and pull requests
- Check commits, branches and pull requests for an entire version within JIRA software
Want to know more? Go here.