Bug Triage Workbench
Rank open issues by impact, reach, reproducibility and age while keeping effort and severity visible.
- 1List your issues
- 2Read the answer as you type
- 3Download or print it
Loading the worked example…
Assumptions
Results update as you type. Example figures are illustrative.
Your working data
Edit cells directly or import a CSV. Download “Input CSV” for the required column names. Up to 200 rows; scroll the table sideways for additional fields.
Detailed analysis
Exports include all results, regardless of the search filter. The HTML report includes assumptions and source data; use your browser’s Print command for PDF.
Chart shows the first 20 rows; negative values use a warm color. Click table headers to sort.
Compare up to four scenarios
Capture the current inputs, change assumptions and capture again. Scenarios are included in downloaded projects.
What this model includes
Custom prioritization formula, not a universal severity standard. Score = severity × reach × reproducibility fraction + age points; closed issues score zero.
Import and save safely
CSV imports use your current assumptions. Project files restore assumptions, rows and saved scenarios. No automatic saving: download a project before closing this page. Imports are limited to 10 MiB and 200 rows. Calculations run in your browser; the site’s advertising and analytics follow its privacy policy.
Using Bug Triage Workbench
Rank open issues by impact, reach, reproducibility and age while keeping effort and severity visible.
- Set the review date and how much age should count.
- List each issue with owner, severity, reach, reproducibility, date, fix hours and state.
- Follow the numbered fix order beside your table, then download it.
Example
The worked example includes Export crash, Misaligned icon, Slow search. Change the first review date setting and compare the result with a saved baseline.
Questions & answers
What does Bug Triage Workbench calculate?
Rank open issues by impact, reach, reproducibility and age while keeping effort and severity visible.
What are the important limitations?
Custom prioritization formula, not a universal severity standard. Score = severity × reach × reproducibility fraction + age points; closed issues score zero.
Can I continue my work later?
Yes. Save a project JSON file and reopen it with Import CSV / project. It contains the working data, assumptions and up to four scenarios. Nothing is saved automatically.
What CSV columns do I need?
bug, owner, severity, reach, repro, opened, effort, state. Download Input CSV for a compatible example. CSV imports keep your current assumptions.
Are these example figures current industry benchmarks?
No. They are illustrative values to demonstrate the model. Replace them with figures appropriate to your situation.
Related tools
A useful next step for your task.
Everyday CalculatorsProject Risk RegisterRank project risks, compare initial and residual exposure, and highlight overdue mitigation actions.
Everyday CalculatorsFMEA Risk AnalyzerCompare failure modes using severity, occurrence and detection scores, then review planned residual scores.
Everyday CalculatorsResource Capacity PlannerCompare team members’ workable hours with planned work, leave and recurring overhead; expose overload by role.
Everyday CalculatorsBackup Retention PlannerEstimate retained backup storage and transfer windows across datasets with full and incremental schedules.
Help improve this tool
Report a problem or suggest an improvement
Describe the issue without pasting private tool input. Feedback goes to our admin inbox.