This page is for installing the JIRA server plugin only.

For instructions on installing the Bonfire browser extensions see Getting Bonfire for your browser.

(warning)  The information on this page does not apply to Bonfire OnDemand. For information on installing Bonfire onDemand, please refer to the Add-ons in OnDemand

1. Check compatibility

Before installing Bonfire, please check that Bonfire is compatible with your version of JIRA and browsers at the Bonfire Compatibility Chart.

2. Get your license

Visit https://my.atlassian.com to get a license key for Bonfire, and save it.

3. Install Bonfire

  1. Click the 'Administration' link in the top right of JIRA to open the JIRA administration console.
  2. Click the 'Plugins' link under the 'Plugins' drop down along the top of the screen. The 'Universal Plugin Manager' will be displayed, showing the plugins installed on your JIRA instance.
  3. Click the 'Install' tab in the UPM. The 'Find new plugin' page will display, showing the featured plugins available for JIRA.
  4. Type 'Bonfire' in the 'Search the Plugin Exchange' box and click the 'Search' button.
  5. Click the 'Install' button for Bonfire. A confirmation message and the plugin details will display, if it is installed successfully.
For more information about installing plugins through the Universal Plugin Manager, please read Installing Marketplace apps

4. Activate Bonfire

  1. Click the 'Administration' link to open the JIRA administration console again.
  2. Go to the 'Bonfire' page under the 'Plugins' section in the top menu.
  3. You will be directed to the Plugins page where you will be prompted to enter your license
  4. If you are not redirected to the plugins page, then it means you version of UPM does not have this feature. Instead you will be taken to the Bonfire License page where you may enter your license.

 

 

  • No labels

2 Comments

  1. Anonymous

    Jun 14, 2012

    My Chrome gave the error message Extensions, apps, and user scripts cannot be installed from this web site.

    The workaround outlined in this article solved my installation problem. 

    1. Gilmore Davidson

      Jun 14, 2012

      This is unfortunately part of Chrome's new extension installation policy, that is currently activated in the Canary (nightly) builds.

      We will be updating documentation about this once the implementation in Chrome has been finalised, hopefully with a whitelist setting.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.