Persona is no longer an option for authentication on BMO. For more details see Persona Deprecated.
Last Comment Bug 86908 - buglist.cgi should also accept spaces for separators in the id parameter
: buglist.cgi should also accept spaces for separators in the id parameter
Status: NEW
Product: Bugzilla
Classification: Server Software
Component: Query/Bug List (show other bugs)
: 2.13
: All All
: P4 enhancement (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
: default-qa
: 97433 (view as bug list)
Depends on:
  Show dependency treegraph
Reported: 2001-06-20 11:14 PDT by bobj
Modified: 2005-07-09 17:45 PDT (History)
4 users (show)
See Also:
QA Whiteboard:
Iteration: ---
Points: ---


Description bobj 2001-06-20 11:14:03 PDT
If you enter "bugs numbered:" separated by spaces as
   86637 80446 84491

Bugzilla generates the buglist using:

Here is the full query:

If you enter "bugs numbered:" separated by '|' as

Bugzilla generates the buglist using:

Here is the full query:

The only way I can get the buglist.cgi to work is by using this for the list:

Here is the full query:

After I hand enter the query that works (above), and I click on 
"Edit this query", it sends me to the query.cgi page and fills "bugs numbered:" 
separated by '|' as

and if you do not edit anything and just click on submit, it will generate
the incorrect query as in the 2nd example above.
Comment 1 Christian Reis 2001-06-25 23:42:57 PDT
Confirmed in current CVS bugzilla. Note that comma-spacing works.
Comment 2 Matthew Tuck [:CodeMachine] 2001-06-25 23:57:33 PDT
OK, weird.

For keywords, we support space and comma, or a sequence of these as a
separator.  We should do the same for bug numbers.

I don't see why we would need to support '|' as a separator.  I think we should
either fail when receiving multiple parameters (if possible), or we should make
sure Edit Query uses ", " as a separator.

Note that two keywords parameters are interpreted as appended together (see bug
#87407, screen 2 attachment).  We should aim for consistency.

It is important that if we have an illegal character, we should fail (for bug
numbers and keywords).

Currently we just take the numeric data before the illegal character as the one
and only bug and give incorrect results silently.
Comment 3 Christopher Aillon (sabbatical, not receiving bugmail) 2001-08-24 18:44:44 PDT
Mass moving to new product Bugzilla...
Comment 4 Matthew Tuck [:CodeMachine] 2001-11-09 09:20:59 PST
*** Bug 97433 has been marked as a duplicate of this bug. ***
Comment 5 Dave Miller [:justdave] ( 2001-11-17 18:20:05 PST
We are currently trying to wrap up Bugzilla 2.16.  We are now close enough to
release time that anything that wasn't already ranked at P1 isn't going to make
the cut.  Thus this is being retargetted at 2.18.  If you strongly disagree with
this retargetting, please comment, however, be aware that we only have about 2
weeks left to review and test anything at this point, and we intend to devote
this time to the remaining bugs that were designated as release blockers.
Comment 6 Joel Peshkin 2004-03-18 07:50:08 PST seems to care about these so they wont make 2.18.  If
someone adopts them, they can move them back. Retargetting to 2.20
Comment 7 Max Kanat-Alexander 2005-03-05 02:40:28 PST
This looks... really simple to handle.
Comment 8 Max Kanat-Alexander 2005-07-09 17:45:11 PDT
This is really trivial, but I don't plan to actually work on it any time soon.

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