This process was slow and disjointed. It discouraged the reporting of minor bugs and created a backlog of "context-less" tickets where developers had to guess the environment in which the error occurred. Bonfire was built to collapse these four steps into a single, seamless action.
#Atlassian #Jira #Bonfire #TestAutomation #DevToolsHistory
Once the best way to report Jira bugs with screenshots & logs. Now: sunset, but not forgotten.
Bonfire 2 Deep Dive: Shared Sessions & Blitz Testing. Atlassian Bonfire 2 makes it easier than ever to collaborate with teammates ... Atlassian Getting started with Capture for JIRA - SI Collaboration JIRA Instantly attach and annotate screenshots to share with your team. * Create a test session with Capture for JIRA. What is a test s... Smithsonian Institution Capture for JIRA - Confluence Creating Sessions * Tip - You can create test sessions using JIRA's keyboard shortcuts and quick access dialogs as well. So you ca... Atlassian Capture for JIRA - Confluence - Atlassian Bonfire was renamed to JIRA Capture in 2.7, aligning the add-on more closely with JIRA. Other features include: new "myActiveSessi... Atlassian Bonfire 2.6 - Add images of native apps - Work Life by Atlassian Oct 30, 2012 — atlassian bonfire
The standout feature of Bonfire was the ability to take a screenshot or record a video directly within the browser context. More importantly, it included annotation tools (arrows, boxes, blurring, text). A tester could circle a misaligned button, blur out sensitive user data in the background, and point to the specific UI element in question—all before the ticket was even created.
: File bug reports directly from your browser without switching between applications.
The tool transformed the browser into a testing platform. Instead of switching contexts, the tester stayed on the page. Bonfire provided a suite of annotation tools that allowed users to markup the screen directly, capturing not just the bug, but the thought process behind the report. This process was slow and disjointed
The platform utilized a dual-component architecture to bridge the gap between active web browsing and issue tracking:
Atlassian Bonfire, now officially known as , is a tool designed to streamline visual feedback and bug reporting for software teams. It allows QA teams, developers, and designers to file comprehensive reports directly from the web application being tested. Core Features of Atlassian Bonfire
The User Interface (UI) of Bonfire was designed to be unobtrusive. It typically resided as a small icon in the browser toolbar. Upon clicking, a sidebar or overlay would slide out from the side of the screen. Atlassian Bonfire 2 makes it easier than ever
: Invite team members into a central forum in Jira to track testing activity for specific stories or requirements.
Bonfire was not just a standalone product; it was a strategic move by Atlassian to lock in their dominance in the agile toolchain. By owning the browser extension layer, Atlassian extended JIRA’s reach from the project management database to the edge of the application layer.
This interface was minimalist. Large buttons for "Capture" and "Record" dominated the top, while a simple text area allowed for a quick summary. The user did not need to navigate complex JIRA forms; they simply typed the bug title, annotated the screen, and hit "Submit." Bonfire handled the mapping of that input to the required JIRA fields behind the scenes.