1158209 - custom fields hidden by the BMO extension should be cleared when a bug is moved to a product/component where they are not valid

Status: NEW

(bugzilla.mozilla.org :: Extensions, defect, P3)

Description

[Dylan Hardison [:dylan] (he/him)]

+++ This bug was initially created as a clone of Bug #825946 +++

tracking/status flags should be cleared when a bug is moved to a product/component where they are not valid.

steps:

1. create a bug in "Core :: Networking: HTTP"
2. set blocking-basecamp --> ?
3. move the bug to "Websites :: Other"

the blocking-basecamp field will remain set, and will show up in queries, however the field is hidden from the UI and cannot be unset.

the field should have been cleared when the bug's component changed.

Comment 1

[David Lawrence [:dkl]]

Should we throw an interim warning page that the flags will be removed and ask for confirmation? My gut says yes as I can see someone doing this mistakenly and then switching back and the flags are no longer set. Of course they are in the history. But this will be a crazy if someone does a mass edit.

Comment 2

[:glob ✱]

(In reply to David Lawrence [:dkl] from comment #1)
> Should we throw an interim warning page that the flags will be removed and
> ask for confirmation? My gut says yes as I can see someone doing this
> mistakenly and then switching back and the flags are no longer set. Of
> course they are in the history. But this will be a crazy if someone does a
> mass edit.

that comment applies to bug 825946 also.

we don't display a confirmation page for flags, which are cleared when bugs are moved, so if that's the direction we want to take it needs to happen on bug 825946 as well as for flags too.

i'm not a fan of the intermediate confirmation page, but it will likely be required here for the non-modal view.
for bug-modal we should build atop bug 1151745, probably adding an icon when fields will be cleared with a tooltip which shows the impacted fields/flags.