Create migration plan for new bug type field
Categories
(bugzilla.mozilla.org :: Administration, task)
Tracking
()
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:
- Change the type of existing bugs in these components
- Change the default type of new bugs filed under these components
- Change the type of bugs with the
enhancementseverity toenhancement - Change the type of bugs with the
polishkeyword toenhancement - Remove the
enhancementoption from the severity field - (TBD) Change the type of bugs with the
metakeyword tometa - (TBD) Remove the
metakeyword
Comment 1•6 years ago
|
||
About meta, you would like to add that as a new value? (with defect/task/enhancement)?
| Assignee | ||
Comment 2•6 years ago
•
|
||
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?
Comment 3•6 years ago
|
||
We can use https://github.com/mozilla/bugbug for the migration, it's quite precise and should be better than handwritten rules.
| Assignee | ||
Comment 4•6 years ago
|
||
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.
I agree, I think we can get away from meta as a bugtype.
| Assignee | ||
Comment 6•6 years ago
•
|
||
So a bit revised plan:
- Change the type of all existing bugs to
defectortaskin according to this spreadsheet using a migration script - Change the default type of new bugs filed under these components using a migration script
- Disable the
enhancementoption from the severity field using a migration script - Change the type of existing bugs with the
enhancementseverity toenhancementusing Dr. Marco’s bugbug - Change the type of other existing bugs to
defectorenhancementusing bugbug
I've reviewed the spreadsheet and updated it.
| Assignee | ||
Comment 8•6 years ago
|
||
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.
Comment 9•6 years ago
•
|
||
(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
| Assignee | ||
Comment 10•6 years ago
|
||
Got it. I’ll write a script to do the work.
| Assignee | ||
Comment 11•6 years ago
|
||
I think the plan is now ready. I’ll send a migration script PR from Bug 1522348.
Comment 12•6 years ago
•
|
||
:marco, can you send me results from a sample run of the bugbug classifer to review?
Description
•