"Priority Flag Alert" mails include a lot of irrelevant components
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
"You're getting this email because some bugs for which you're the triage owner or the triage owner deputy have no priority set."
From discussion, this email is actually sent to every peer in a managers' group and contains all components anyone is a triage owner for, so if those peers triage a bunch of components, the email ends up having 99% irrelevant content - that's not actionable for the receiver.
These should be split up. The higher-up-manager may still get the overall view, but team leads should only get the information about the components they actually triage, i.e. have some control over.
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 by tracing the code that sends the "Priority Flag Alert" emails and how it selects recipients and components. Compare the current manager-group behavior with the requested split: team leads should receive only components they triage, while the higher-up manager may retain the overall view.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100