If you are anything like us with your development processes, then you would probably track all your development work – be they bugs, improvements, or features – in an issue tracker like JIRA. You would also use a CI tool too, like Bamboo, to run builds constantly to make sure that your code base remains in good health – at least most of the time. What we wanted is a nice way to bring our issues and builds together so we have one consolidated view of issues, and builds. This is where Bamboo 2.1 and JIRA comes in.
When you commit your source code, you might typically add in the JIRA issue you are working on into the commit message. Bamboo picks this up, and recognizes that it’s a JIRA issue. You can do the link up yourself too, either by commenting on a build in Bamboo, labelling it, or making the link directly. Fear not if you make a mistake, just remove the link and add a new one. This attaches your builds to the issue. In your JIRA issues page, you now get an issue tab showing me the builds that ran for the issue. Artifacts produced by the build are handily available to download, direct from JIRA. You can also view your builds on the version level, and project level too.
Issue builds link.png
One of the issues that we have sometimes faced is figuring out, during the development of a version, when an issue is fixed. In JIRA, an issue may be marked as “fixed” against version X, but while that version X isn’t released, it is difficult to find out in which build it actually is fixed. Now with the click of a button, you can get around this by promoting a build linked to an issue as a “fixed” build. It is an easy to track down to the exact build an issue is fixed in.
Change to fixed.png
For most sizable projects in JIRA, you would probably have set up multiple plans to run different builds. Confluence, for example, has plans set up to run unit tests on JDK1.4 or functional tests using Tomcat, to name a few. With the project builds tab panel, you can now get the latest status for all your plans for your project. A plan is determined to be part of the JIRA project, if a build in the plan is related to an issue in the project. This idea is extended further to each version. In the version builds tab panel, you can see how your builds are going for a particular version, based on the fix-for version of the issues your builds are relate to. But what happens when the version is released? Any builds that happen on your plans are no longer affecting the released version. In this case, the version builds tab panel finds the release date, and shows the latest status (snapshot) of each of the affected plans before the release date.
version builds.jpg
Have you ever wondered which JIRA issues your team is currently working on? In JIRA, you can always use the issue navigator to find the list of issues sorted by last update date. But this doesn’t necessarily tell you those issues under active development. Using the issues tab under a plan summary in Bamboo, you can now find out, sorted by date, those issues that you’ve worked on recently, filtered down by the handy date filters in Bamboo.
Recent active issues.png
For managing release, you can also check out the new JIRA versions release management plugin, developed by Jonathan Djokovic. The plugin uses JIRA’s versions to help you automate your release process.
You can start using all these features today, with Bamboo 2.1. Learn more here.

Fresh ideas, announcements, and inspiration for your team, delivered weekly.

Subscribe now

Fresh ideas, announcements, and inspiration for your team, delivered weekly.

Subscribe now