369995 - Values of an obsolete drop down custom field cannot be deleted if some bugs use these values

Status: NEW

(Bugzilla :: Administration, task, P4)

Description

[Frédéric Buclin]

If a drop down custom field is made obsolete, you cannot delete any of its values (in editvalues.cgi) used by bugs, because the UI to edit this field is no longer available in show_bug.cgi.

So we should either hide the "There are N bugs with this field value. You must change the field value on those bugs to another value before you can delete this value." message in editvalues.cgi and replace it by another message explaining why this value cannot be deleted, or we should allow to force these bugs to fallback to --- which we know always exists.

Note also that the link given in the message above no longer work, because Search.pm seems unable to look for obsolete fields and returns all bugs from the DB instead.

Comment 1

[Max Kanat-Alexander]

Why would you want to delete any values used by an obsolete field?

Comment 2

[Frédéric Buclin]

That's not the question(*). The UI lets you do it, that's all. And as such, we should display something reasonable.

(*) One answer could be: because we are doing QA tests right now.

Comment 3

[Max Kanat-Alexander]

(In reply to comment #2)
> And as such, we should display something reasonable.

  Okay. We should just forbid people from editing the values of an obsolete field, then. I think that's simplest. It would clean up the UI for people who have lots of obsolete fields, anyway.