Bonfire Troubleshooting Guide

Bonfire license does not match JIRA license

I am receiving an "invalid license" message even though my license key is correctly pasted from my.atlassian.com.
Bonfire and JIRA user license tiers have to match in order for Bonfire license to accept it. If you would like to trial Bonfire - feel free to use a free 30 day evaluation license by going to my.atlassian.com.

Bonfire browser extension is on a beta version, but the server plugin is already running 1.0.

I am receiving a "404" error in the browser extension when trying to login.
Bonfire's beta browser extensions are not compatible with the final 1.0 (or above) server plugin. You can verify this by checking the server plugin version (in UPM on JIRA) and the browser extension (in the browser's extension manager). Both versions should have the same number before the first "."
To fix, un-install and reinstall the browser extension from the JIRA's "Get Bonfire" page. The browser extension will not auto-update. For more details about upgrading from beta - please follow: Upgrading from Bonfire Beta to 1.0 guide.

Remote API calls are not turned on on the JIRA server.

I receive a "Remote API not turned on" message.
Check the "Accept remote API calls" setting under "General Configuration" of the JIRA server.

Invalid license or beta not activated

I receive a "Bonfire not activated" message.

If the beta is not activated, or license is invalid, Bonfire browser will not connect to the server. Check your license on the JIRA server

Cookies are not enabled

I receive a "Invalid username or password" message even though I am sure my username and password is correct.

Bonfire requires cookies to work. Turn on cookies for the browser.

User does not have "JIRA User" Permission

I receive a "Remote Permission Exception" when trying to login.

The remote API will not allow connections for a user if they do not have the "JIRA User" permission. On the server, any user who has "JIRA Administrator" permission but no "JIRA User" permission will still be able to login. However, that's not the case for the remote API. Ensure users have "JIRA User" permission.

Customer running 4.3.x and the user is from a LDAP user repository

I receive a "Invalid username or password" message even though I am sure my username and password is correct.

There was a bug in embedded Crowd in JIRA which causes issues for REST authentication (including Bonfire). To resolve this, there are two workarounds for this:
1 - Start JIRA with the following JVM argument:-Datlassian.org.osgi.framework.bootdelegation=sun., com.sun., org.springframework.ldap.core.*2 - Before trying to log in via the browser extension, first log into JIRA via the web interface.

Currently running Bonfire 1.0 Beta instead of final

We were experiencing this issue during Bonfire beta. We've resolved it in 1.0. Please upgrade to Bonfire 1.0.

A mandatory field is not being shown on the create issue form. Related to the issue above.

We were experiencing this issue during Bonfire beta. We've resolved it in 1.0. Please upgrade to Bonfire 1.0.

User does not have permission to create issue

To verify, try and create the issue using JIRA's web interface. Bonfire respects JIRA's permission for issue creation.

Assignees invalid.

There may be a misconfiguration in the project which has a default assignee for the project, but the default assignee does not have assignable permissions in the project. To verify, try and create the issue using JIRA's web interface. Bonfire respects JIRA's permission for issue creation.

Attachments are turned off

If attachments are turned off in the system, then Bonfire will fail to attach the screenshot (which is an attachment). Turn on attachment.

User does not have edit permission on an issue

Although it may appear that Bonfire is creating the issue and uploading in one go, the attachment of the screenshot is actually an edit on the issue created. If the user does not have edit permission, they cannot attach the screenshot.

Using variables in the Create Issue tab rather than in a template.

Variables can only be used in an issue template, not in the create issue form. The issue will create with variables unevaluated (e.g. '

')

Invalid JS selector in the variable

Variables are based off simple javascript selectors, and if selector is invalid/doesn't evaluate, the form will show up with the variable with errors filled in (instead of expected value). To verify, try and evaluate the variable on the screen they are creating the bug on. To do this, invoke Bonfire from the screen you want to raise the bug on, then go to the Templates tab. Under there, find the variable you are using, and then click the little "eye" - which will evaluate the javascript in a dialog.

Bonfire prior to version 1.0.2 had this issue

Update Bonfire to 1.0.2.