I talked to andre__ a bit about it (maemo bugmaster), and when bugzilla gets upgraded to 3.4 a "ON_QA" may be added. I suggested following this typical (though maybe a bit slow by Fedora standards) bug report as an example:
https://bugzilla.redhat.com/show_bug.cgi?id=538118

They had a bug, they had a source fix, and had even pushed out a *binary* fix to the public before the status was changed. And even though they have a binary fix in the public, it is still not *CLOSED*, it is "ON_QA". Then when it hits their final repos, it gets closed.

That seems to be a very good way to do it and it seems to me that Maemo (Nokia) should look to Fedora (Red Hat) as a model because they are doing things very well and are in a similar type of situation (e.g. large corporation heavily involved in a "community" distribution).

Every time you CLOSE a bug with "fixed internally, if you don't know how to build a .deb, go wait", you annoy your customers. WORKSFORUSWAITFORITNOOB, is not the best status...

-Jeff