Closed
Bug 237188
Opened 21 years ago
Closed 21 years ago
no search results for milestone with a comma in the name
Categories
(Bugzilla :: Query/Bug List, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 205861
People
(Reporter: mturner, Assigned: justdave)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
When trying to search for bugs with a milestone with a space in the name, no
results are found.
Bugzilla version 2.16.3
Platform and browser independant
Reproducible: Always
Steps to Reproduce:
1.Create milestone with space in the name ("March 11, 2004")
2.Place a bug in the target milestone
3.Search for bugs for the milestone
Actual Results:
No results where found
Expected Results:
Bug placed in the milestone should be found.
Reporter | ||
Updated•21 years ago
|
Version: unspecified → 2.16.3
Comment 1•21 years ago
|
||
I had a quick look at this in passing, as I have milestones with space in them
on my bugzilla installation. WORKSFORME with space....
Given the example cited, ("March 11, 2004"), it would be the comma rather than
the space that causes the problem. Bugzilla takes this as being a separator.
Updating summary ("space" -> "comma")
Essentially, %urlbase%/buglist.cgi?target_milestone=March+11%2c+2004
is interpreted as a search for bugs with a target milestone of either
"March 11" or " 2004".
Summary: no search results for milestone with a space in the name → no search results for milestone with a comma in the name
Comment 2•21 years ago
|
||
hmmmm.... is this close enough to Bug 205861 to be considered a dupe?
Reporter | ||
Comment 3•21 years ago
|
||
Yes, it would be a dup of bug 205861 (and marking it so) - we even use the same
type of example to tickle the bug.
*** This bug has been marked as a duplicate of 205861 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Updated•12 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
•