bugbot resets the priority field for completely wrong reason
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
related to https://github.com/mozilla/bugbot/issues/2829
https://bugzilla.mozilla.org/show_bug.cgi?id=2023633#c3
the timeline is the following:
- the bug was filed in the correct component
- the bug got a priority
- the bugbot closed the bug as invalid, moving the component (https://github.com/mozilla/bugbot/issues/2829), this is simply wrong
- I undo-ed thhe bugbot's action, reopened the bug, moved the bug back to the correct component
- the bugbot resets the priority field, saying that the component is changed
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 reading issue #2829 and the linked Bugzilla report to understand the component-change behavior and the priority reset. Trace the bugbot path that handles these metadata changes; done means undoing or reopening a component change does not incorrectly reset an existing priority.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100