For bugs that are marked Confidential (currently Netscape Confidential, and in the future Mozilla Confidential when we get the system finished), we need a field listing external users who are also permitted to view/edit the bug in spite of the fact that it's marked Confidential. This will enable efficient cooperative work with customers on bugs that reveal customer confidential information. Example: right now I'm working on two bugs for enablement of a particular market share tracking software. The bugs have been marked Confidential at the request of the customer because the reports reveal detailed information about how their software works. But now only Netscape and Mozilla staff can see the bug, and the engineers at that company (who are actually going to implement the fix!) can't view or edit the bug, and they're having to email update requests to the bug report (and requests to be emailed the latest version) to our administrator.

see also bug 39816

Thought - always allow assigned to, reporter, qa contact and cc users to read bug?

CC/Reporter/Owner, etc. is what bug 39816 is all about (but keeping it optional). ekrock@netscape.com, is that what your after here? If so, please mark this a dupe.

*** This bug has been marked as a duplicate of 39816 ***

moving to Bugzilla product reassign to default owner/qa for INVALID/WONTFIX/WORKSFORME/DUPLICATE

Verified dupe