Don't reset priority when bugs are moved from one non-untriaged component to another
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
Edge case I missed in #493: batch moves of bugs from one component to another as part of a reorganization of bugs.
When bugs are moved "silently" (no-email sent) don't reset priority.
Moves are shown as done by a list of no-email addresses:
- nobody@mozilla.org
- bug-husbandry-bot@mozilla.bugs
Example of priority resets: https://mzl.la/2XAEMhX
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
Trace the handling of batch component moves and priority updates, using the two listed no-email addresses as the condition to investigate. Confirm the behavior around silent moves between non-untriaged components; done means those moves preserve the existing priority while ordinary moves retain their current behavior.
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
- 42/100