Before long, the development community realized that it was helpful to plan all code changes with an issue tracker and then to reference the issue ID in the commit message.
From its lowly beginnings as an bug tracker, JIRA has grown into a collaborative project management system that helps developers connect the dots. Today, JIRA is a master of integration: It’s become the spider at the center of a web of change.
Let’s take a look at how JIRA integrates with other members of the web-based Atlassian Suite.
JIRA with Bitbucket Source Control
JIRA with HipChat messaging client
A very good use of a Confluence JIRA macro is to create a simple change log (shown). The filter can reference the JIRA issues by version. Here, the best practice is to work from the Bitbucket commits, so that the change log only includes issues that changed the source code. Pretty simple, since Bitbucket automatically links each JIRA ID back to its issue.
When tied with Confluence, JIRA automatically surfaces “mentions” of JIRA IDs on Confluence pages. So, if you have a test plan in Confluence, and quite sensibly include the JIRA ID, JIRA says “aha!” and links the issue with the page on its own. It’s so automatic that you don’t even have to press a button!
For more about HipChat integrations, see this Atlassian blog.
JIRA with Agile
As Salesforce and Scrum developers, we find JIRA fits our process like a glove. As a DevOps engineer, I enjoy being able to surf between JIRA, Bitbucket, Confluence, and HipChat, to be sure all my ducks are still in a row.