Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BugBot is too keen to move bugs to components ("search", "bookmarks"), despite previous examples of moving them back. #2566

Open
Standard8 opened this issue Dec 17, 2024 · 2 comments

Comments

@Standard8
Copy link
Member

STR

  1. The update_bot files a bug in Fenix::General for an application services update.
  2. The update happens to mention search (amongst other things).
  3. botbot comes along and moves it to Fenix::Search.
  4. We then move it back to Fenix::General because it isn't specific to search.
  5. Wait to the next update and go back to the first step.

Actual Results

Every time there's a release, someone has to move the bug back again.

Expected Results

The bot should learn, or be able to be told never to move bugs like this.

As a side note, I've also seen that the bot appears to be overly keen to move bugs. I'm pretty sure that in a lot of instances the first comment only has to have the word "search" in it to be moved to the search component (of Fenix or Firefox), and similarly "bookmarks" to get to the Bookmarks & History component in Firefox, even though the bug might be talking about address bar or profiles.

@Standard8
Copy link
Member Author

A couple of examples:

Not all of the bugs starting "Update android nightly application-services..." do get moved, but a lot of them do and then we have to move them back again...

@marco-c
Copy link
Contributor

marco-c commented Jan 8, 2025

We should just exclude bugs filed by updatebot from the component assignment, as we can expect them to always be correct.

@marco-c marco-c transferred this issue from mozilla/bugbug Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants