[severity_underestimated] Avoid to nag when the severity has been set after the dups.
Open
Nobody has claimed this yet.
area-Noise Reduction
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
For example:
https://bugzilla.mozilla.org/show_bug.cgi?id=694856
Severity has been decided after the dups have been added so it doesn't make sense to nag here.
@suhaibmujahid, could you have a look please ?
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
No file or test is named. Start by tracing the severity-underestimated reminder for the linked Bugzilla case, then verify the reminder is suppressed when severity was set after duplicates were added.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100