View Single Post
Andre Klapper's Avatar
Posts: 1,665 | Thanked: 1,649 times | Joined on Jun 2008 @ Praha, Czech Republic
#15
Originally Posted by igor View Post
And if the bug is assigned originally to component B, but then it is discovered to belong to component A, what happens to all the previous discussion? Does it get censored?
In the long run we must have exactly one bug tracking system. Suse e.g. have one bugtracker and use the "insider group" functionality in Bugzilla to have bug reports and/or comments/attachments only visible to employees if chosen, but they only deal with software.
Having secret hardware information too makes this a much more complicated problem to solve. Fixing some upstream issue in Mozilla Bugzilla e.g. about being able to set the visiblity of specific fields (hardware info etc) might help.

Originally Posted by igor View Post
Or, even worse, bug in component X, from a previous sw release is obsoleted by the fact that component X is going to be dropped/replaced but that is not public yet. What should we do?
Of course I got exactly the same problem here. Often being silent by non commenting. And a small number of my "I don't know" comments in the public Bugzilla are actually lies, thanks to the NDA.
__________________
maemo.org Bugmaster