100050 - Bugzilla doesn't handle space when parsing bug IDs

Status: RESOLVED WONTFIX

(Bugzilla :: Bugzilla-General, defect)

Description

[Jerome Lacoste]

I don't really know if it is a RFE or a bug.
As shown in the text of bug 9940 (in 'Additional Comments From Ben Bucksch
2001-09-17 00:11'), bugzilla doesn't handle a space in the bug number and
doesn't create the correct link.
As bug IDs are over 100 000, it should perhaps handle it?

Comment 1

[Jacob Steenhagen]

100 000 isn't a number... it's two numbers (one hundred & zero)... bugs should
be referenced by numbers (all digits, no spaces/punctuation), not "shorthand".

Recommend WONTFIX.

Comment 2

[Jerome Lacoste]

Isn't the comma separated number an american notation ?
In France we use a space.

Comment 3

[Jacob Steenhagen]

It vary well may be (I'm American, and I use a comma).  I think some countries
use a period.  My take on this is that bug numbers should have NO delimters. 
There is already a precident for this in Bugzilla as accourding to American
grammer rules, any number greater than 9999 has to have a comma in it (the comma
is optional at 1,000 but is required at 10,000).

Comment 4

[Matthew Tuck [:CodeMachine]]

I recommend an underscore.  No one uses it (I think), so we aren't biasing
towards anyone.

Comment 5

[Gervase Markham [:gerv]]

People seem perfectly happy typing bug numbers as e.g. bug 100000, without the
need for any separators. ParseUrls has already been rewritten for speed once;
I'd be worried about complicating the regexps in it any further.

Gerv

Comment 6

[Gervase Markham [:gerv]]

WONTFIX.

Gerv

Comment 7

[Dave Miller [:justdave]]

clearing target on DUPLICATE/WONTFIX/INVALID/WORKSFORME so they'll show up as
untriaged if they get reopened.