bugbot resets the priority field for completely wrong reason

Open
#2,830 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
tooling

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.

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
Dominant language
Python
Stars
68
Forks
92
Avg merge
2d 2h
Merged PRs (30d)
16

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mozilla/bugbot

All issues in mozilla/bugbot

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.