When severity is set to N/A for a defect, mention it is not a valid value instead of asking to set severity
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
See:
https://bugzilla.mozilla.org/show_bug.cgi?id=1964247#c23
I set the severity/priority yesterday, but BugBot still said the severity wasn't set.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Bugzilla report and trace the severity validation that produces the reminder when a defect has severity set to N/A. Reproduce the case described there; done means the message identifies N/A as invalid rather than asking the user to set severity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100