Good admins help their teams find tools that make their processes easier. Great admins help their teams integrate their tools for elevated productivity, collaboration, and speed.
Integrating Bitbucket and Jira can provide numerous benefits for dev teams and Jira administrators.
Devs- Integrating Bitbucket and Jira through this app eliminates the need for constant context switching between tools, allowing them to track code changes and work items in one central location. This can lead to improved collaboration among team members and foster better communication.
Admins- Gain increased visibility on the status of key projects allowing them to make more informed decisions, Having access to real-time information on code changes also allows admins to more accurately estimate lead times and set realistic deadlines.
We recommend creating a Bitbucket user specifically for the integration. This way, the Bitbucket user can have defined permissions to perform given tasks. Ensure this user has access to the repositories that you wish to integrate with Jira.
To continue your Bitbucket Jira integration, you’ll need to install Git Integration for Jira from the Atlassian marketplace. Like all Atlassian marketplace apps, you’ll need a Jira administrator to install the app. Once you have Git Integration for Jira installed, you can begin connecting your Bitbucket repositories with the associated Jira projects.
At this point, the app will index your repositories and make them available to be viewed in Jira.
To create a link between a Git commit and a Jira issue, developers must include the Jira issue key in their commit message.
Example Git commit message: GIT-4322 – Updated the plugin …
In this example above, GIT-4322 is the Jira issue key linking the commit message to the Jira issue. Commits that are part of non-main branches will be included only if the main branch doesn’t have them.
Pro Tip: When working with a sub-task, put the parent and sub-task Jira issue keys in the commit message so that the commit shows in both places. This way, the commit for the sub-task does not get lost in the many commits of the parent issue.
On your Jira Cloud instance, open a Jira issue. On the Jira Git integration development panel, click [Open Git integration] then click [Create branch]. This will open a dialog box where the branch can be created.
The newly-created branch is now associated with that Jira issue listed in the development panel under Branches. Perform a commit to the newly-created branch to be ready for merge.
To create a pull request from a Jira issue, open the desired Jira issue, click Open Git integration then click Create pull request. This will open a dialog box where the merge request can be made.
Pull requests are still indexed based on branch name even if the PR title does not have the Jira issue key – as long as the branch name contains the Jira issue key. Preview allows you to see the comparison view of the current changes in the selected Source branch vs Target branch (usually main).
By default, repositories are reindexed on a fixed interval. If you want Jira to reflect Bitbucket updates in real time, you must set up Webhooks. To add webhooks to your connected Bitbucket repositories, complete the following steps.
Next, you'll need to go to Bitbucket to finish the integration.
Your webhook is now created. Commits, branches, and merge requests that are associated with a Jira issue will now be visible in Jira issues in real-time.
Start a free trial of Git Integration for Jira. Your developers will love the time it saves them and you will appreciate the visibility it affords you.
Want to take your Jira Bitbucket integration to the next level? See how you can start leveraging Jira Smart Commits to perform actions in Jira like making a comment or record time tracking using just your Git commits.
Ken Paetzold
Dev Collaboration Evangelist
GitKraken
Scottsdale
0 comments