Closed Bug 239912 Opened 16 years ago Closed 16 years ago

bug_email.pl doesn't work with useqacontact

Categories

(Bugzilla :: Creating/Changing Bugs, defect, trivial)

defect
Not set
trivial

Tracking

()

RESOLVED FIXED
Bugzilla 2.16

People

(Reporter: matthew, Assigned: matthew)

Details

Attachments

(2 files)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040206 Firefox/0.8
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040206 Firefox/0.8

bug_email.pl has a bug - it sets the "qacontact" field rather than the
"qa_contact" field.  

Easy fix, line 832 of latest CVS:

-     $Control{'qacontact'} = FetchOneColumn();
+     $Control{'qa_contact'} = FetchOneColumn();



Reproducible: Always
Steps to Reproduce:
Submit mail to a component with a default QA contact

Actual Results:  
Bug doesn't have a qa contact

Expected Results:  
Bug should have a QA contact
Assignee: myk → mmastrac
Status: UNCONFIRMED → NEW
Ever confirmed: true
Target Milestone: --- → Bugzilla 2.16
Severity: normal → trivial
Status: NEW → ASSIGNED
Flags: approval?
Flags: approval2.16?
Summary: [patch] bug_email.pl doesn't work with useqacontact → bug_email.pl doesn't work with useqacontact
Comment on attachment 145647 [details] [diff] [review]
Patch for the 2.16 branch

r=vladd on both branches (the patch is written by Matthew, I'm just uploading
the diff as attachment)
Attachment #145647 - Flags: review+
Attachment #145648 - Flags: review+
Vlad- Thanks for creating the patch!
Flags: approval?
Flags: approval2.16?
Flags: approval2.16+
Flags: approval+
Checking in contrib/bug_email.pl;
/cvsroot/mozilla/webtools/bugzilla/contrib/bug_email.pl,v  <--  bug_email.pl
new revision: 1.9.12.3; previous revision: 1.9.12.2
done

Checking in contrib/bug_email.pl;
/cvsroot/mozilla/webtools/bugzilla/contrib/bug_email.pl,v  <--  bug_email.pl
new revision: 1.20; previous revision: 1.19
done
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.