What makes a good bug report?
A good bug report lets someone else reproduce the problem without asking: a specific title, numbered steps, the expected and the actual result, the environment (build, browser, device, account), data used, and evidence such as a screenshot or log. Severity describes the impact on the system (a crash, data loss); priority describes how soon the business wants it fixed — the two are set separately and often differ.
Read the guide: How to Write a Bug Report
A Critical bug that can wait
A critical defect in a rarely used feature with a workaround
- Known severity:
- Critical
- Pushes the priority down:
- affected users: a rarely used feature · workaround: exists
- Pushes the priority up:
- none stated
- Suggested priority:
P2: may reasonably wait
A Minor bug that cannot
A minor defect blocking a contractual demo
- Known severity:
- Minor
- Pushes the priority down:
- none stated
- Pushes the priority up:
- customer commitment: a contractual demo is blocked
- Suggested priority:
P0
The page’s exampleExample
A NaN total blocks payment in promotion week; release in 10 days
- Known severity:
- not stated
- Pushes the priority down:
- none stated
- Pushes the priority up:
- revenue impact: direct, during the campaign
- Suggested priority:
P0: fix immediately (hotfix)
The FAQ’s two cases and the page’s example. Severity has its own row; the push rows name the other factors each case states, using the tool’s factor names (the tool marks every factor, severity included, as up, down or neither).
How to use AI Bug Priority Suggestion
- Paste the bug report.
- Describe the business context — release dates, affected customers, how often it happens, revenue or contractual impact — and set the known severity, or leave it as Not assessed.
- Pick the output language and press Suggest priority.
- Read which factors push the priority up or down, check the recommended fix window, and answer the questions to confirm.
AI Bug Priority Suggestion features
- P0–P3 recommendation that combines severity with business context
- Shows which factors push the priority up or down
- Recommended fix window (hotfix, current sprint, next release…)
- Confidence and questions to confirm
AI Bug Priority Suggestion example
Priority
Input:
NaN total blocks payment; promotion week; release in 10 daysOutput:
P0 — Fix immediately (hotfix): direct revenue impact during the campaignFrequently asked questions about AI Bug Priority Suggestion
Why can a Critical bug get P2?
Because priority weighs business context: a critical defect in a rarely used feature with a workaround may reasonably wait, while a minor defect blocking a contractual demo becomes P0.
What if I do not know the severity yet?
Leave it as Not assessed. The tool then weighs the report itself and states its assumptions, which lowers the confidence; the AI Bug Severity Suggestion tool can rate the severity first.
What is the recommended fix window?
When to fix, in your own terms — for example a hotfix today, a named sprint or the next minor release — based on the dates and commitments you described.
Technical notes
The result is a priority from P0 (fix immediately, as a hotfix) to P3 (fix when convenient), a 0–100 confidence, the reasoning, the business factors considered — severity, affected users, frequency, revenue impact, deadline or release, customer commitment, regulatory or compliance constraints, workaround, reputation, effort to fix — each marked as pushing the priority up, down or neither, a recommended fix window and questions to confirm.
References
- ISTQB GlossaryThe standard definitions of testing terms — test case, regression testing, severity, priority, boundary value analysis and the rest.
- Lessons Learned in Software Testing: A Context-Driven Approach (Cem Kaner, James Bach, Bret Pettichord)Practical lessons on bug reporting, test design, automation and managing testing — the context-driven school.