Closed Bug 1524738 Opened 6 years ago Closed 6 years ago

Create migration plan for new bug type field

Categories

(bugzilla.mozilla.org :: Administration, task)

Production
task
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: kohei, Assigned: kohei)

References

Details

All existing bugs will be defaulted to the defect type, but bugs in some components have to be task or enhancement. I’m compiling a list of these components to make the migration easier.

We need a migration script which does something like this:

  1. Change the type of existing bugs in these components
  2. Change the default type of new bugs filed under these components
  3. Change the type of bugs with the enhancement severity to enhancement
  4. Change the type of bugs with the polish keyword to enhancement
  5. Remove the enhancement option from the severity field
  6. (TBD) Change the type of bugs with the meta keyword to meta
  7. (TBD) Remove the meta keyword

About meta, you would like to add that as a new value? (with defect/task/enhancement)?

Yes, that’s what I’m suggesting in Bug 1522342.

  • A meta bug can be a collection of defects, enhancements, tasks or mixture of them. Even if it’s simply a list of regressions, the meta bug itself is not a defect, so labelling and tracking it as the defect type may not make sense.
  • Also, the summary of many meta bugs contains [meta] or [tracking] partially thanks to the auto nag script but for me it looks redundant and inconsistent.

Introducing the meta type aims at solving these issues. What do you think?

We can use https://github.com/mozilla/bugbug for the migration, it's quite precise and should be better than handwritten rules.

From the RM analysis meeting yesterday and my thoughts on the Target Milestone field, we apparently don’t need the meta type. I’d rather like to ditch the meta keyword by making milestones usable.

Blocks: 1522348

I agree, I think we can get away from meta as a bugtype.

So a bit revised plan:

  1. Change the type of all existing bugs to defect or task in according to this spreadsheet using a migration script
  2. Change the default type of new bugs filed under these components using a migration script
  3. Disable the enhancement option from the severity field using a migration script
  4. Change the type of existing bugs with the enhancement severity to enhancement using Dr. Marco’s bugbug
  5. Change the type of other existing bugs to defect or enhancement using bugbug
Flags: needinfo?(ehumphries)

I've reviewed the spreadsheet and updated it.

Flags: needinfo?(ehumphries)

I was about to write a script to do 1, 2 and 3, but do we have any existing tool to bulk-edit bugs without updating the last changed date? If so only 2 needs a migration script, I guess.

Flags: needinfo?(ehumphries)

(In reply to Kohei Yoshino [:kohei] (Bugzilla UX) (FxSiteCompat) from comment #8)

I was about to write a script to do 1, 2 and 3, but do we have any existing tool to bulk-edit bugs without updating the last changed date? If so only 2 needs a migration script, I guess.

This script is similar but would need to be updated to do the specific changes you re looking for

https://github.com/mozilla-bteam/bmo/blob/master/scripts/resolve_bugs.pl

Got it. I’ll write a script to do the work.

I think the plan is now ready. I’ll send a migration script PR from Bug 1522348.

Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED

:marco, can you send me results from a sample run of the bugbug classifer to review?

Flags: needinfo?(mcastelluccio)
Depends on: 1536304
Depends on: 1548022
You need to log in before you can comment on or make changes to this bug.