Modern software teams are shipping software faster than ever before.
With the adoption of continuous delivery and other practices like feature flagging, different pieces of your software are ready to be released to customers at any time. In the past, when a feature was released, it was a big deal. The whole company would spend days or even weeks preparing for the single release. But today, organizations who have adopted modern development practices have a different problem: Every day is launch day.
As development speed increases and the number of items being worked on continues to grow, teams involved in the delivery process, all the way from product to support, find they lack visibility into what is being developed, deployed, and released to customers, when, where, and by whom.
Today, we’ve stepped up the integration between Jira Software Cloud and Bitbucket Cloud so teams can gain continuous visibility from their backlog through to release. Teams can now see Bitbucket release information from Jira Software and teams using Bitbucket, can view Jira issues from the Deployment preview screen.
Let’s take a closer look at the new integration.
Deployment visibility in Jira Software
With Bitbucket Pipelines and Deployments enabled, you can gain visibility into the release status of all your Jira issues from the Jira issue view. Release information that was once locked in your deployment tools, only visible to your dev team, is now visible to any team member working in Jira Software.
Release status at your fingertips
Anyone involved in the delivery process can self-serve release information from the Jira issue instead of having to ping someone in a chat room. Product Management, Support, and even Marketing teams can view what issues or features have been deployed to customers and which are still waiting in staging environments. This means product leaders spend less time updating people on their status and more time focusing on building great products.
Dive deeper into the history of releases
Understand the history of releases by clicking on the release status and view all of the environments – test, staging or production – that each issue has been deployed to, along with information about when the changes were deployed to that environment. This is valuable to engineers who want to see a history of an issue progressing through the release environments or for QA teams to see when a commit moves from Test to Staging. Failed deployments are also highlighted so the team knows when something didn’t make it through and can investigate further.
No longer is release information scattered across multiple tools, locked in the release manager’s head or being pinged across a chatroom. Teams that work outside of Bitbucket, now have a centralized place to see all the build and release information related to their project.
Now what about technical teams who work from Bitbucket?
Tying Jira issues and releases together in Bitbucket Deployments
Using the Deployment preview, development teams can quickly validate what code they are about to promote to another environment before hitting Deploy. This preview provides them with all the associated commits, diff and now Jira issues for a higher level of context. By clicking on the issue key, they can view and even edit the Jira issue without leaving Bitbucket.
Confidence in your promotions
A complete history of releases
The deployment history helps teams diagnose any issues that may arise after a release. They can view a complete history of what was released to each environment, and when. Having visibility into what issues were updated during a past release can speed up the investigation of the error. You can see exactly who pushed the release and connect the right team members associated with the ticket. Combining this with the diff of all code changes that were part of the deployment can help developers pinpoint the exact change that caused the issue.
Jira and Bitbucket can be connected in seconds. Once they’re connected, Bitbucket Pipelines deployment information will be automatically pushed into Jira and associated Jira issues will be exposed in the Bitbucket Deployments dashboard.
With Bitbucket Pipelines, there is no separate tool to manage or users to synchronize, everything there, built-in Bitbucket.
Give the new integration a try
First connect Jira and Bitbucket, and then add an issue key to the commit message that triggers your deployment step. For example, typing:
git commit -m "PT-323 Add created workers to container cluster"
will connect your deployment with issue PT-323, and you are ready to go!
Learn more about how Jira and Bitbucket work together.
Have a question, comment, or want to suggest a pipe that should be built next? Discuss Bitbucket Pipes with the Bitbucket team in the Atlassian Community here.