From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020830
Description of problem:
Red Hat's Bugzilla seems to only recognize one style of an embedded bug numbers
for auto-hyperlinking. While many people specify "Bug <number>", there are
quite a few (including Red Hat employees) which specify an alternative format
that is not recognized as an embedded Bug Number.
See "Expected Results" for examples.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Browse the bugs in Red Hat's Bugzilla.
2. Browse the bugs in Mozilla's Bugzilla.
Actual Results: Red Hat's Bugzilla only recognizes "Bug <number>" format.
Expected Results: Red Hat's Bugzilla should recognize quite a few formats
(through simple regex additions):
Bugs <number>, <number>
Bugs #<number>, #<number>
Bug ID <number>
Bug ID #<number>
Bugs 78688, 34222
Bugs #78688, #34222
Bug ID 78688
Bug ID #78688
The new bugzilla system also does hyperlinking to the same extent so I will need
to pass this change upstream to the core developers.
Well, the "new" 2.17.1 release (from 2.8 ... very interesting) seems to capture
more auto-linking than the previous Bugzilla. But I don't understand why "Bug
ID <number>" is captured but "Bug ID #<number>" is not. Since I have not delved
into the source code of Bugzilla - can't you add templates for the auto-linking?
Bug match = Bug, Bug #, Bugs, Bugs #, Bug ID, Bug ID #
Buglist match = #,+# (or something horked up like that).
bugs 123 and 456
bugs 123, 456 and 789
Red Hat's current Bugzilla version is 2.18. I am moving all older open bugs to
this version. Any bugs against the older versions will need to be verified that
they are still bugs. This will help me also to sort them better.
Still there (see comment #2 and comment #4).
I have updated the section of code responsible for linking to the latest from
upstream BZ which should help a little. Any other linking misses should be filed
in a bug report at http://bugzilla.mozilla.org.