Wildcard rejects --do_not_change-- in mass-change

RESOLVED FIXED in Bugzilla 2.18

Status

()

P2
major
RESOLVED FIXED
16 years ago
6 years ago

People

(Reporter: bugreport, Assigned: erik)

Tracking

2.17
Bugzilla 2.18

Details

Attachments

(1 attachment)

(Reporter)

Description

16 years ago
When a form indicates --do_not_change-- as, for example, QA contact, the
wildcard feature complains that the string did not match anything.  This is true
even in wildcard mode where there shoudl be no reason for wildcard to look
anything up unless there is a "*" in it.
(Reporter)

Comment 1

16 years ago
The right thing to do for this is probably for the patch not to judge if a
string matches nothing.  If a string cannot find a record, it can be left
untouched just as if the wildcard patch had not existed.
Severity: normal → major
Status: NEW → ASSIGNED
Priority: -- → P2
Target Milestone: --- → Bugzilla 2.18
(Assignee)

Comment 2

16 years ago
Created attachment 104798 [details] [diff] [review]
allows --do_not_change-- to pass through without scrutiny

This patch compares the value of the 'dontchange' field passed by the form to
the field in question to determine whether it should be skipped over.  Same way
process_bug.cgi does it.
(Reporter)

Comment 3

16 years ago
Comment on attachment 104798 [details] [diff] [review]
allows --do_not_change-- to pass through without scrutiny

r=joel
Attachment #104798 - Flags: review+
(Reporter)

Comment 4

16 years ago
Checked in for not_erik:

Checking in Bugzilla/User.pm;
/cvsroot/mozilla/webtools/bugzilla/Bugzilla/User.pm,v  <--  User.pm
new revision: 1.4; previous revision: 1.3
done
Status: ASSIGNED → RESOLVED
Last Resolved: 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.