Bugbot moves metabugs that have dependencies and priority/severity set (iow are perfectly triaged) filed by editbugs users to random other components

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

Start with the linked Bugzilla example, 1880897#c1, and trace the Bugbot path that moves metabugs filed by editbugs users. Identify how dependencies and priority/severity are represented, then define and test signals that prevent well-triaged metabugs from being moved to another component. Done means such metabugs remain in their intended component.

Written by the indexing model from the issue text.

Description

area-Noise Reduction

This is tedious: https://bugzilla.mozilla.org/show_bug.cgi?id=1880897#c1 .

Can we teach it not to do this? Don't know off-hand which are the best signals to avoid doing this but it seems to me there are several here.

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.