Atlassian Bonfire ships with custom fields that can be searched using JQL.
Custom Fields
Atlassian Bonfire has the following custom fields:
| Name | Supported Versions | Description |
|---|---|---|
| Bonfire User Agent | Bonfire 2.2+ | Stores the raw User Agent of the reporter of an issue created using Atlassian Bonfire. Only visible on the Bonfire web panel on the View Issue page. |
| Bonfire Browser | Bonfire 2.2+ | Stores the Brower Info of the reporter of an issue created using Atlassian Bonfire. Only visible on the Bonfire web panel on the View Issue page. |
| Bonfire Operating System | Bonfire 2.2+ | Stores the Operating System Info of the reporter of an issue created using Atlassian Bonfire. Only visible on the Bonfire web panel on the View Issue page. |
| Bonfire URL | Bonfire 2.2+ | Stores the URL of the page an issue created using Atlassian Bonfire was on. Only visible on the Bonfire web panel on the View Issue page. |
| Bonfire Screen Resolution | Bonfire 2.2+ | Stores the Screen Resolution for the reporter of an issue created using Atlassian Bonfire. Only visible on the Bonfire web panel on the View Issue page. |
| Bonfire jQuery Version | Bonfire 2.2+ | Stores the jQuery Version of the page an issue created using Atlassian Bonfire was on. Only visible on the Bonfire web panel on the View Issue page. |
| Bonfire Document Mode | Bonfire 2.5+ | Stores the Document Mode of the page an issue created using Atlassian Bonfire was on. Only visible on the Bonfire web panel on the View Issue page. |
| Test Session(s) | Bonfire 2.1+ | Lists the Bonfire Test Sessions that are related to this issue. |
| Raised During | Bonfire 2.1+ | Shows the Bonfire Test Session that this issue was raised during. |
| Testing Status | Bonfire 2.4+ | Shows the total testing status of this issue using all of the Bonfire Test Sessions related to this issue. |
All custom fields in Bonfire are created programmatically using custom fields types that are bundled with Atlassian Bonfire. Using these custom field types for fields not generated by Bonfire is not recommended.
All of these custom fields can be used in JQL to find issues.
Useful JQL Commands
You will need to re-index your JIRA instance before any searches in JQL will work properly.
These JQL commands are examples of the types of searches that can be done using the Bonfire Custom Fields.
Overview
Content Tools
Apps
Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.