When notifying about bugs without severity, add triage owner name for each bug to clear confusion
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
The auto rotation for triage got me scheduled to be triage owner for WebExtensions components this week. I just got an email with 3 different bugs, two were from our components, but the third one Bug 1749345 clearly wasn't, nor was it moved into/out of one of our components.
It looks like our bugzilla query is wrong, including product: Toolkit and component: General, which it shouldn't.
https://mzl.la/3pDk1Pk
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. Trace the Bugzilla query used for triage-owner notifications, starting with the filters that include product Toolkit and component General, then inspect how bug details are assembled for email. Done means unrelated bugs are excluded and each notified bug identifies its triage owner.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100