How to use AI Bug Severity Suggestion
- Open the tool and paste the bug report.
- Optionally add context (feature description, acceptance criteria, environment) — the more concrete the input, the better the result.
- Pick the options (count, output language, focus) and press the action button.
- Review the structured result in the table, then copy or download it as Markdown, CSV or JSON.
AI Bug Severity Suggestion features
- Standard rubric: Blocker, Critical, Major, Minor, Trivial
- Factor-by-factor assessment (functional impact, data integrity, security, scope, workaround, frequency…)
- Confidence score and borderline alternative
- Questions to confirm when information is missing
- Choose English, Arabic or Hindi for the generated text — identifiers, HTTP methods and technical tokens always stay in English.
AI Bug Severity Suggestion example
Severity
Input:
Discount code applied twice → NaN total, payment blocked, reload restoresOutput:
Critical (80% confidence): payment blocked for all customers using codes; workaround exists but is not discoverableFrequently asked questions about AI Bug Severity Suggestion
What is the difference between severity and priority?
Severity measures technical and user impact; priority measures business urgency. Use the companion Bug Priority Suggestion tool for the second.
Is my input stored?
No. Your text is sent to the Mutqan AI service and the structured result is returned to your browser. We do not store prompts or outputs — only anonymous usage counters used for daily limits.
How many generations can I run?
Anonymous visitors get a small daily allowance per network address; registered users get a higher daily quota. The remaining count is shown under every result.
Can I get the result in Arabic or Hindi?
Yes — choose the output language. Natural-language fields are written in that language while identifiers, HTTP methods, paths and other technical tokens stay in English.
Technical notes
Your input is sent to the Mutqan AI service over an encrypted connection; prompts and results are never stored — only anonymous usage counters used for rate limiting.
The AI must answer with strict JSON that is validated against a schema on the server before anything is rendered; malformed answers are retried once and then rejected with a clear message.