In our installation of Bugzilla, we do not use the UNCONFIRMED state. There is no special problem with this, but we still can see it in the query page. Is there a way to hide it?

I'm doing something similar for resolutions over at bug #94534. My current policy is that it appears on the query page if it's active (to avoid "where is it?" questions) or it's in the database. At the moment statuses aren't customised (bug #37613), but even while they're hardcoded, the UNCONFIRMED status should still follow the same rules and not appear if it's not used for any products and is not on any bugs.

Moving to new Bugzilla product ...

correcting version field lost in product move

This should come free as a part of an implementation of customised statuses (bug #101179).

We are currently trying to wrap up Bugzilla 2.16. We are now close enough to release time that anything that wasn't already ranked at P1 isn't going to make the cut. Thus this is being retargetted at 2.18. If you strongly disagree with this retargetting, please comment, however, be aware that we only have about 2 weeks left to review and test anything at this point, and we intend to devote this time to the remaining bugs that were designated as release blockers.

I'll do that as a part of customised statuses.

Enhancements which don't currently have patches on them which are targetted at 2.18 are being retargetted to 2.20 because we're about to freeze for 2.18. Consideration will be taken for moving items back to 2.18 on a case-by-case basis (but is unlikely for enhancements)

Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004. Anything flagged enhancement that hasn't already landed is being pushed out. If this bug is otherwise ready to land, we'll handle it on a case-by-case basis, please set the blocking2.20 flag to '?' if you think it qualifies.

Here is a simple little trick to strip out UNCONFIRMED if there are NO active products that use it. Should be all that is needed, since UNCONFIRMED doesn't appear to be injected at any point.

Comment on attachment 512798 [details] [diff] [review] Code Patch Ver 1 This is not the right fix. What we need to do is to not hardcode UNCONFIRMED anymore.

Comment on attachment 512798 [details] [diff] [review] Code Patch Ver 1 Ah, no, removing it from get_all isn't the right solution--I think that you want some frontend solution instead. Also, why not just tell people to disable the unconfirmed status itself in Field Values (perhaps we don't allow that)?

(In reply to comment #11) > Ah, no, removing it from get_all isn't the right solution--I think that you > want some frontend solution instead. I don't want a front end solution, it could touch too many places. If UNCONFIRMED isn't used anywhere, then it shouldn't be listed as a valid status. > Also, why not just tell people to disable the unconfirmed status itself in > Field Values (perhaps we don't allow that)? Unconfirmed cannot be disabled: "Enabled for bugs: This value is non-deletable and cannot be disabled. "