Bug 406681 - 4.21: Better private/public visibility of specific Bugzilla attributes
Summary: 4.21: Better private/public visibility of specific Bugzilla attributes
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: 3.6
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Simon Green
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-11-30 17:13 UTC by David Lawrence
Modified: 2014-10-12 22:45 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-19 04:02:42 UTC
Embargoed:


Attachments (Terms of Use)

Description David Lawrence 2007-11-30 17:13:00 UTC
Description:
A special 'public' checkbox (or group) that make the main details of the bug visible to the everyone, even though the bug may belong to one or more private groups (perhaps also hiding the reporter's name).\n The 2-state 'private' checkbox against each comment becomes tri-state

Requester:
Alasdair Kergon

Comment 1 David Lawrence 2007-11-30 17:28:19 UTC
A special 'public' checkbox (or group) that make the main details of the bug
visible to the everyone, even though the bug may belong to one or more private
groups (perhaps also hiding the reporter's name).

The 2-state 'private' checkbox against each comment becomes tri-state:
(1) visible only to RH
(2) visible only to RH plus the groups the bug belongs to (and reporter/cclist
if checked)
(3) visible to everyone when the bug is marked 'public' - otherwise same as 2

A 'Visibility' of exactly one of 'Red Hat OR Partner OR Public' would be
selected against each comment.  [Obviously the exact wording is open to debate -
'Groups' rather than 'Partner' for example - or use multiple checkboxes.]
Then it would be possible for many of the bugs that today have to be kept
private because they contain information we only want the reporter/partner
groups/cclist to read to be made visible to everyone and we could still have
comments there restricted to partners & issue tracker.


Comment 2 David Lawrence 2008-08-18 21:11:08 UTC
Voting for future Bugzilla features will be opening soon. Announcement of start date will be posted to the bugzilla-development-list and other broader audience.

Dave

Comment 3 David Lawrence 2010-01-15 17:32:27 UTC
Red Hat Bugzilla is now using version 3.4 of the Bugzilla codebase and
therefore this feature will need to be implemented against the new release.
Updating bug version to 3.2.

Comment 4 David Lawrence 2010-08-25 21:42:48 UTC
Red Hat has now upgraded to Bugzilla 3.6 and this bug will now be reassigned to that version. It would be helpful to the Bugzilla Development Team if this bug is verified to still be an issue with the latest version. If it is no longer an issue, then feel free to close, otherwise please comment that it is still a problem and we will try to address the issue as soon as we can.

Thanks
Bugzilla Development Team

Comment 6 Jeff Fearn 🐞 2012-05-30 04:43:56 UTC
As part of the recent Bugzilla 4.2 upgrade the Bugzilla team are cleaning up bugs opened against old versions of Bugzilla. This bug has been flagged as an old bug and will be CLOSED WONTFIX in 7 days time.

If you believe this bug is an issue in the latest Bugzilla version please comment on this bug within 7 days. Doing so will ensure this bug is not closed automatically.

Thanks, the Bugzilla team.

Comment 7 Jeff Fearn 🐞 2012-05-30 04:44:26 UTC
As part of the recent Bugzilla 2.4 upgrade the Bugzilla team are cleaning up bugs opened against old versions of Bugzilla. This bug has been flagged as an old bug and will be CLOSED WONTFIX in 7 days time.

If you believe this bug is an issue in the latest Bugzilla version please comment on this bug within 7 days. Doing so will ensure this bug is not closed automatically.

Thanks, the Bugzilla team.

Comment 8 Alasdair Kergon 2012-05-30 09:02:42 UTC
Still should be changed IMO

Comment 9 Simon Green 2012-06-19 04:02:42 UTC
(In reply to comment #8)
> Still should be changed IMO

This won't happen. At the core of Bugzilla, a private bug is not viewable if you are not able to see the bug. For us to break this will require the Red Hat Bugzilla team would need to maintain its on security on bug information, and that is not feasable.


Note You need to log in before you can comment on or make changes to this bug.