286333 - review/super-review and first-review/second-review attachment flags cleared when changing bug product(/component)

Status: RESOLVED WONTFIX

(bugzilla.mozilla.org :: General, defect)

Description

[Serge Gautherie (:sgautherie)]

Take bug 280485 as an example:

Moved bug from Toolkit to Core component,
lost the first-review/second-review attachment flags :-(

Either the flags should be the same everywhere,
or the should be kept/migrated when changing the bug !?


I'm not too familiar with these 2 "new" *-review flags,
but the current behaviour is odd anyway.

Comment 1

[Dave Miller [:justdave]]

This works as designed.  Flags are only valid for specific product/component
combinations, and are defined with different people who get email for them or
different access restrictions depending on the product/component.  That
information is no longer valid in a new component, so the flags are removed. 
The previous information about those flags is still available in the activity log.

Comment 2

[Serge Gautherie (:sgautherie)]

(In reply to comment #1)
> This works as designed.

Well, I can understand that.

(Oh ... I notice that I used 'Component' where I meant 'Product'...)

Yet, could there be a warning, as in such a case I may prefer to cancel the 
(product) change, or in any case to know what is going to happen before 
validating my change:

When changing the product, I get a page to select the new 
version/component/target: this is where/how I'd like to see the added warning 
about which attachment flags will be removed.

Can I reopen for this "morphed" request ?

Comment 3

[Serge Gautherie (:sgautherie)]

(In reply to comment #2)
> Yet, could there be a warning, as in such a case I may prefer to cancel the 
> (product) change, or in any case to know what is going to happen before 
> validating my change:

As a reminder to set the new review (request) flags for example...

Comment 4

[Dave Miller [:justdave]]

see bug 274802