Closed
Bug 177624
Opened 22 years ago
Closed 22 years ago
Wildcard rejects --do_not_change-- in mass-change
Categories
(Bugzilla :: User Interface, defect, P2)
Tracking
()
RESOLVED
FIXED
Bugzilla 2.18
People
(Reporter: bugreport, Assigned: erik)
Details
Attachments
(1 file)
1.02 KB,
patch
|
bugreport
:
review+
|
Details | Diff | Splinter Review |
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•22 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•22 years ago
|
||
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•22 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•22 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
Closed: 22 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•