1141452 - Adjustment on the project flags (blocking-b2g and tracking-b2g)

Status: RESOLVED FIXED

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

Description

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

[Description]
Remove "blocking-b2g:backlog" and "tracking-b2g:?". New attribute "tracking-b2g:backlog" will be created instead.

[Migration plan]
1. add the attribute "tracking-b2g:backlog"
2. move current "blocking-b2g:backlog" and "tracking-b2g:?” bugs to "tracking-b2g:backlog". (If a specific bug originally has tracking-b2g:+ or tracking-b2g:-, let's just keep the way it is.)
3. remove both attributes "blocking-b2g:backlog" and "tracking-b2g:?”.

[Access]
Everyone has the ability to set to tracking-b2g:backlog.
The group of people having access to "blocking-b2g"(Kilimanjaro Drivers) should have access to set +,- on tracking-b2g. 

[Note]
Definition of the flags are on WIKI.
https://wiki.mozilla.org/B2G/Triage#Project_Flags

Comment 1

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

Is it possible that migration plan (step2) can be done in a batch (w/o needing to make it bug-by-bug)?

Comment 2

[:glob ✱]

currently there are 2272 bugs with blocking-b2g:backlog, of which 1087 are still open.
tracking-b2g:? has 94 bugs, with 78 open.

should this apply to all bugs, or just open bugs?

we can deactive the old values so old bugs with, for example, blocking-b2g:backlog set will still show that value, however it won't be a selectable option.

> Is it possible that migration plan (step2) can be done in a batch (w/o
> needing to make it bug-by-bug)?

yes; at the bottom of a search result is a 'change several bugs at once' link which can be used to make bulk updates.  unfortunately that will trigger bugmail for every change, making it generally unsuitable for updates of this size.

to make these changes we'll probably have to write a small script that updates the database directly.  not a big deal, but it will impact the time it takes to make this change.

do you have a timeframe for when you'd like to see this done?

Comment 3

[:glob ✱]

administrative note - the steps we'll have to take are:

if all bugs need to be updated, regardless of open/closed status:

1. develop, test, review, and deploy a script which
   - changes blocking-b2g:backlog to tracking-b2g:backlog on all bugs without triggering bugmail
2. mark the blocking-b2g:backlog value as inactive
3. rename tracking-b2g:? to tracking-b2g:backlog
4. execute the script developed in (1)
5. delete blocking-b2g:backlog

if only open bugs needs to be updated:

1. develop, test, review, and deploy a script which
   - changes blocking-b2g:backlog to tracking-b2g:backlog on open bugs without triggering bugmail
   - changes tracking-b2g:? to tracking-b2g:backlog on open bugs without triggering bugmail
2. mark the blocking-b2g:backlog and tracking-b2g:? value as inactive
3. create tracking-b2g:backlog
4. execute the script developed in (1)

Comment 4

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

(In reply to Byron Jones ‹:glob› from comment #2)

> should this apply to all bugs, or just open bugs?
To all bugs. This adds more consistency when in the future people query these old bugs.
(I'm assuming there's not much extra efforts to do so)

> do you have a timeframe for when you'd like to see this done?
Not urgent. So let's say around 3/17 (PST)?

Comment 5

[:glob ✱]

Attachment: 1141452_1.patch

Comment 6

[David Lawrence [:dkl]]

Comment on attachment 8578034 [details] [diff] [review]
1141452_1.patch

Review of attachment 8578034 [details] [diff] [review]:
-----------------------------------------------------------------

Need to change the tracking_flag_id value and not the 'backlog' value for all flags found.

Comment 7

[:glob ✱]

Attachment: 1141452_2.patch

d'oh.

Comment 8

[David Lawrence [:dkl]]

Comment on attachment 8578047 [details] [diff] [review]
1141452_2.patch

Review of attachment 8578047 [details] [diff] [review]:
-----------------------------------------------------------------

Looks/works good. r=dkl

Comment 9

[:glob ✱]

To ssh://[e-mail]/webtools/bmo/bugzilla.git
   5365c22..894d016  master -> master

Comment 10

[:glob ✱]

i forgot to take into account what needs to happen if a bug has both blocking_b2g:backlog set and the tracking_b2g is already set.  in this case we should just delete the blocking_b2g:backlog value.

To ssh://[e-mail]/webtools/bmo/bugzilla.git
   6da6c66..f48c489  master -> master

Comment 11

[:glob ✱]

flags updated.

Comment 12

[:glob ✱]

Attachment: update log

Comment 13

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

Thank you very much. Byron.