Bug 134278 – Removing QA Contact does not actually remove

Bug 134278 - Removing QA Contact does not actually remove

Summary:	Removing QA Contact does not actually remove

Status:	CLOSED NEXTRELEASE

Aliases:	None

Product:	Bugzilla
Classification:	Community
Component:	Bugzilla General (Show other bugs)
Sub Component:
Version:	2.18
Hardware:	All Linux

Priority	medium Severity medium (vote)
Target Milestone:	---
Target Release:	---
Assigned To:	Mike MacKenzie
QA Contact:	David Lawrence
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2004-09-30 16:29 EDT by David Lawrence
Modified:	2007-04-18 13:13 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2004-10-25 11:58:29 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description David Lawrence 2004-09-30 16:29:48 EDT

Description of problem:
Clearing out the qa_contact field on a bug/feature report does not
cause the database column to be cleared out. More than likely the code
is only looking for a change and not the absence of the qa_contact
variable. So we will have to explicitly check for it in process_bug.cgi

Note: I had the same problem in 2.17 so the code could be copied from
there if it has a fix.

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

Comment 1 Mike MacKenzie 2004-10-25 10:34:49 EDT

Can I add myself to the cc list and reassign to me at the same time?

Comment 2 Mike MacKenzie 2004-10-25 10:36:48 EDT

Yes. I can.  This needs to be fixed, too...

Comment 3 Mike MacKenzie 2004-10-25 11:58:29 EDT

This now works correctly.   The qa contact will be cleared from the database is
the form field is blank (or has any false value).

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