Bug 132004

Summary:	QA contact was removed instead of my email added to cc:
Product:	[Community] Bugzilla	Reporter:	Eugene Kanter <ekanter>
Component:	Bugzilla General	Assignee:	PnT DevOps Devs <hss-ied-bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.2	CC:	leon, myk
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
URL:	https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=131974
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-11-07 16:23:00 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Eugene Kanter 2004-09-07 19:03:42 UTC

Description of problem:

bugzilla removed QA contact from the record.

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


How reproducible:
unknown.

Steps to Reproduce:

This is what I have done: 
1. started from clean cookie cache - no login remembered.
2. clicked on https://bugzilla.redhat.com/bugzilla/show_bug.cgi?
id=131974 link sent to me via email.
3. clicked on "Add Me to Cc List" cleck box.
4. received login promp, logged in.
5. got standard update responce page with email sent to owners, etc.

  
Actual results:

1. my email is NOT on cc: list.
2. all recepients received an update message

ekanter changed:

          What    |Removed                     |Added
-----------------------------------------------------------------
         QAContact|bbrock           |



Expected results:

1. my email is added to cc: list
2. appropriate email is sent to everybody on the bug list.

Comment 1 Myk Melez 2004-11-17 14:24:10 UTC

Removal of the QA contact just happened to me as well over in bug
139457 when I submitted a comment on the bug.  I did not try to add
myself to the CC list, however, so it may be a different bug, or
perhaps multiple kinds of changes trigger the same bug.

Comment 2 David Lawrence 2006-04-08 17:53:06 UTC

Red Hat's current Bugzilla version is 2.18. I am moving all older open bugs to
this version. Any bugs against the older versions will need to be verified that
they are still bugs. This will help me also to sort them better.

Comment 3 David Lawrence 2008-09-16 16:51:06 UTC

Red Hat Bugzilla is now using version 3.2 of the Bugzilla codebase and therefore this bug will need to be re-verified against the new release. With the updated code this bug may no longer be relevant or may have been fixed in the new code.
Updating bug version to 3.2.