Highlights of this release:

Upgrading Bonfire?

Atlassian Bonfire 2.2 includes updates to the JIRA server plugin, as well as major updates to client browsers. All browser extensions will need to be upgraded by visiting the "Get Bonfire" page from your JIRA instance after the server plugin is upgraded. For more information on upgrades, check out our Capture for JIRA Upgrade Guide.

Please note that since Firefox 3.6 reached End-Of-Life status on April 24, 2012, Bonfire 2.2 and later will no longer support Firefox 3.6.

Field visibility control for templates

We've had plenty of requests to be able to hide specific issue fields when using a template in Bonfire, and this was the first feature we wanted to put into Bonfire 2.2.

Checkboxes on the template form control field visibility when the template is used, so that you can choose to view only the fields that matter to you. These hidden fields will also apply for anyone using your shared template.

Mandatory fields that are required for issue creation will always be visible, to minimize the chance of issue creation errors.

"Sticky" templates

Using a template in Bonfire has previously been a "fire and forget" action. That is, once a template was chosen it was forgotten about, forcing you to choose it again for the next issue.

We realised this was a pain point for customers, so we've made big changes to the way templates and variables work.

Now when you use a template, it will continue to be used until you choose otherwise – even across restarts of the extension. Creating an issue will reset the form back to the default state of the template, letting you create consistent issue reports even faster.