QA Commander — Bug Tracker, Test Runs & Quality Audits
by Dot BD Solutions Limited https://dotbdsolutions.com$ 99.99
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Project (project) |
| Lines of code | 3794 |
| Technical Name |
qa_bug_tracker |
| License | OPL-1 |
| Website | https://dotbdsolutions.com |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Project (project) |
| Lines of code | 3794 |
| Technical Name |
qa_bug_tracker |
| License | OPL-1 |
| Website | https://dotbdsolutions.com |
| Versions | 18.0 19.0 |
Your Entire QA Workflow, Inside Odoo.
Stop switching between Jira, spreadsheets, and email threads. QA Commander is the only Odoo module that combines bug tracking, sprint test runs, QA audits, and printable PDF reports in one place — the way real QA engineers actually work.
Bug Tracker • Test Runs • QA Audits • PDF Reports • Re-Test Workflow
Before vs. After
Without QA Commander
✗ Bugs logged in Excel no one keeps updated
✗ No link between a bug and its sprint or release
✗ Re-test results lost in Slack messages
✗ QA audit reports typed manually in Word
✗ No idea how many bugs slipped into production
✗ Paying for Jira just to share with your Odoo team
With QA Commander
✓ Every bug auto-numbered BUG-0001 with full lifecycle
✓ Sprint / release field links each bug to the right cycle
✓ Re-Test stage with Pass / Fail buttons and date stamp
✓ QA Audit checklist with 1–5 scoring and PDF sign-off
✓ Detection Phase field measures defect leakage instantly
✓ Everything lives inside your Odoo — free from Jira
Report Bugs Directly from Tasks
Inside any Odoo Project task, two new buttons appear at the top: Report Bug and Create Test Case. Your team logs bugs without leaving the task they are working on. Bug count smart buttons show live on every task.
The bug is linked to the task, the project, the sprint, and the tester who found it — all automatically.
Auto-Sequenced Bug IDs
Every bug gets a unique auto-generated ID: BUG-0001, BUG-0002, and so on. No manual numbering, no duplicates, no confusion.
The list view shows severity badges, priority stars, assignee, stage, and navigation path — everything the QA team needs at a glance. Multi-edit lets you triage 20 bugs in 30 seconds.
Structured Bug Reports
Each bug report captures exactly what real QA engineers need:
✓ Navigation Path — Settings → Account → Password
✓ Severity badge (Blocker / Critical / Major / Minor / Trivial)
✓ Bug Type (Functional, UI/UX, Security, Regression…)
✓ Reported By and Responsible QA are separate fields
✓ Detection Phase (Testing vs Production — for leakage rate)
✓ Sprint / Release and Found in Version
Reproduction Steps Tab
A dedicated tab for the full reproduction workflow: numbered steps, reproducibility rating, frequency count, expected result, and actual result side by side.
Developers get everything they need to reproduce and fix the bug. No more back-and-forth emails asking “how do I reproduce this?”
Environment & Device Tracking
Capture where the bug was found with precision. Built from real QA bug reports that track:
✓ Environment Profile (Dev / Staging / UAT / Production)
✓ OS & Browser (e.g. Windows 11, Chrome 120)
✓ Device Model (e.g. Motorola Edge 70, Samsung S24)
✓ URL / Screen and Module / Area
✓ Application Version (e.g. 19.0.1.0.0)
Structured Test Cases (TC-0001)
Write and manage test cases with auto-sequenced IDs (TC-0001). Each test case has:
✓ Preconditions, Test Steps, Test Data, Expected Result
✓ Draft → Active → Deprecated lifecycle
✓ One-click Run Test to log an execution
✓ Report Bug button directly from test case
✓ Pass Rate computed across all execution runs
Execution History & Pass Rate
Every test execution is recorded with: result (Pass / Fail / Blocked / Skipped), executor, date, duration, build version, and environment.
The system calculates the Pass Rate % automatically across all runs. A failed execution creates a bug report in one click with all context pre-filled.
Everything Your QA Team Needs
Eight core features. All integrated. No extra subscriptions.
Bug / Issue Reports
Auto-sequenced BUG-0001 IDs. Severity, priority, navigation path, device model, OS, browser. Works for software defects, process issues, and service issues.
Re-Test Workflow
After a fix: click Send for Re-Test. QA clicks Re-Test: PASS or FAIL. Date stamped, chatter logged. Warning ribbon on every card pending re-test.
Test Runs (Sprint / Release)
Group test executions by sprint. Auto-sequenced RUN-0001. Live KPI dashboard: pass rate, bugs found, critical bugs. Sign-off by Project Manager. Printable summary PDF.
QA Audit Checklist
Formal audit with 1–5 scoring per criterion. Tracks Meets Standards, Minor/Major Concerns, recommendations. Computed score %. Prepared By / Approved By sign-off. PDF Audit Report.
Defect Leakage Tracking
Tag each bug with the SDLC phase it was found in: Testing/QA, UAT, or Production. Filter “Found in Production” instantly shows your defect leakage rate — the industry’s most important KPI.
6 PDF Reports
Bug Report PDF — single bug, full detail.
Bug Summary List — selected bugs as a table (like Excel).
Project QA Health — severity breakdown + leakage.
Test Run Summary — KPI table + signature block.
Sprint / Release Report — full sprint retrospective.
QA Audit Report — 1–5 scores + sign-off.
Test Cases (TC-0001)
Preconditions, numbered steps, test data, expected result. Track pass rate across runs. One click to run and record. Link failing tests directly to bug reports.
Navigation Path Field
Track exactly where a bug is found: Registration → OTP, Settings → Account → Password. Shown on Kanban cards and in PDF reports. Built from how real QA engineers actually log bugs.
10-Stage Bug Lifecycle
Ships pre-configured. Add, rename, or reorder freely.
6 PDF Reports — One Click Download
Every report is printable as a professional PDF directly from Odoo. No export to Excel, no copy-paste into Word.
Bug / Issue Report
Single bug PDF with full detail: classification, environment, OS, browser, device, steps to reproduce, expected vs actual result, resolution, timeline.
Open any bug → Print PDF button in header
Bug Summary List
Printable table of selected bugs — like John’s Excel sheet but as a PDF. Columns: Bug ID, Title, Module, Severity, Priority, Type, Stage, Assigned To, Days Open. Color-coded by severity.
Bug list → select bugs → Actions → Bug Summary List
Project QA Health Report
Full project quality snapshot: total/open/closed bugs, severity breakdown, bugs by type, defect leakage by detection phase, critical bug table, test coverage stats. Signature block for QA Lead + PM.
Open project → QA Report smart button
Test Run Summary
Per-sprint PDF: run info, KPI table (total tests / pass / fail / blocked / pass rate), bug summary, conclusion, risks. Signature block with sign-off date.
Open test run → Test Run PDF button
Sprint / Release Report
Full sprint retrospective PDF: every test execution logged (result, executor, date, duration, bug created), all bugs found with severity and re-test status. Ideal for sprint review meetings.
Open test run → Sprint Report PDF button
QA Audit Report
Formal audit PDF: score dashboard (total score, avg, %, concerns count), full checklist table, conclusions, concerns, recommended actions. Prepared By and Approved By signature block.
Open audit → Print Audit Report button
How to download a report: Click the print button → Odoo generates the PDF automatically → your browser downloads it. All reports also appear in the Print menu (printer icon) when records are selected in list view. No extra configuration needed.
Why QA Commander
Everything your QA team needs — built into the Odoo you already use.
✓ Auto-sequenced IDs — BUG-0001, TC-0001, RUN-0001, AUDIT-0001
✓ Navigation Path — track exactly where a bug was found
✓ Re-Test Workflow — Pass / Fail buttons with date stamp
✓ Sprint & Release Tracking — link bugs to the right sprint
✓ Detection Phase — measure defect leakage automatically
✓ Device Model — e.g. Motorola Edge 70, Samsung S24
✓ Test Runs with KPI Dashboard — pass rate, bugs found, sign-off
✓ QA Audit Checklist — 1–5 scoring, major/minor concerns
✓ 6 PDF Reports — one-click download, no export to Word or Excel
✓ Works for any project — software, product, service, non-technical
✓ No extra groups needed — any internal user can start immediately
✓ Multi-company aware — respects Odoo company isolation
Compatibility
Compatible with Odoo 19 Community and Odoo 19 Enterprise.
Depends only on the built-in project, mail, and portal modules.
No third-party Python packages required.
Odoo 19 Community Odoo 19 Enterprise
Support & Contact
Need help? We respond within 24 hours.
Dot BD Solutions Limited
Copyright © 2026 Dot BD Solutions Limited. All rights reserved.
Author: Rafiur Rahman Rafit
Licensed under OPL-1
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module