Lower the severity automatically to S4 if we close a bug as INVALID, INACTIVE, INCOMPLETE, EXPIRED, DUPLICATE
Open
Nobody has claimed this yet.
area-Severity
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
When we close a bug as INVALID, INACTIVE, INCOMPLETE, EXPIRED, DUPLICATE this bug can be considered to not have been severe. In order to consider it well in post-close calculations (like the maintenance effectiveness metric) we should update its severity to be lowest.
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
The issue names no files, tests, or entry points. Start by tracing how Bugzilla bug closure reasons are processed and how severity is updated, then identify existing tests for closure handling; done means each listed closure reason results in the lowest severity and post-close calculations use that value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100