Bug 745948 - do not complain about publicly viewable bug, when the sole reason is the reporter being non-RH
Summary: do not complain about publicly viewable bug, when the sole reason is the repo...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: 3.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ---
Assignee: Simon Green
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-13 14:05 UTC by Paolo Bonzini
Modified: 2014-10-12 22:47 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-13 14:22:50 UTC


Attachments (Terms of Use)

Description Paolo Bonzini 2011-10-13 14:05:14 UTC
Description of problem:
If a bug is only visible to Red Hat people, but was reported by a non-RH person, then it makes no sense to ask for restricting the access (the reporter cannot be changed).

Version-Release number of selected component (if applicable):
3.6

How reproducible:
100%

Steps to Reproduce:
1. find a bug that is reported by a non-RH person (e.g. bug 697021) on partner-bugzilla.redhat.com
2. type a test comment to find "watched" and non-RH people
3. go back, remove those people from Cc, qa-contact, etc.
  
Actual results:
BZ still complains about the reporter, and asks you to restrict the bug

Expected results:
There's no point in asking, because the reporter is there and you can't change it.

Additional info:
If the bug is public, but the reporter and everyone else (including their watchers) is a RH employee, the UI doesn't trigger and lets you add comments without asking.

A less intrusive alternative could be to check for RH-ness when the bug is _viewed_, and toggle the default for comments and attachments from public to private if the bug is not pure RH.

Comment 1 Simon Green 2011-10-13 14:22:50 UTC
This is intended functionality.

https://engineering.redhat.com/trac/bugzilla/wiki/Watchers


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