Severity and Priority are in the database as literal values not nubers.
Kerry, Richard
I've just noticed that the Severity and Priority values are held in Bugzilla's database as strings, not as numbers which I'd have expected.
I found this as I noticed that some css styles for Severities weren't being obeyed. And we have our Severities changed from the defaults. And they did, until I just changed them, contain spaces.
The spaces were a problem because the styles used for these use the values of the fields to generate the style names, and these can't contain spaces. Also it seems to me that if the names can be customized from the GUI the styles ought not to stop working as a result.
Might I suggest that these two fields should be stored as numbers, not strings.
I guess I should add this as a bug/feature request ?
Appreciatively,
Merry Christmas,
Richard.
Richard Kerry
Colledia Control Engineer
Siemens IT Solutions and Services Ltd
Room 457 Drama Building, BBC Television Centre, Wood Lane, London, W12 7RJ
T: +44 (0)20 82259063 F: +44 (0)20 8576 8182 M: +44 (0)7921 244993
Email: richar...@siemens.com<blocked::mailto:richar...@siemens.com>
Website: www.siemens.co.uk/it-solutions<blocked::outbind://47/www.siemens.co.uk/it-solutions>
This e-mail contains confidential information and is for the exclusive use of the addressee/s. If you are not the addressee, then any distribution, copying or use of this e-mail is prohibited. If received in error, please advise the sender and delete it immediately. We accept no liability for any loss or damage suffered by any person arising from use of this e-mail.
Siemens IT Solutions and Services Limited
Registered No: 1203466 England
Registered Office: Faraday House, Sir William Siemens Square, Frimley, Camberley, GU16 8QD
Gervase Markham
>
> I've just noticed that the Severity and Priority values are held in
> Bugzilla's database as strings, not as numbers which I'd have
> expected. I found this as I noticed that some css styles for
> Severities weren't being obeyed. And we have our Severities changed
> from the defaults. And they did, until I just changed them, contain
> spaces. The spaces were a problem because the styles used for these
> use the values of the fields to generate the style names, and these
> can't contain spaces. Also it seems to me that if the names can be
> customized from the GUI the styles ought not to stop working as a
> result.
Quite so. The correct fix is to filter the names through the
"css_class_quote" filter, which I believe is designed to turn strings
into valid CSS class names.
Feel free to file a bug on this :-)
Gerv
Kerry, Richard
Seems to be a comment on bug 445296 (so I've commented on it), though with connections to bugs 374473 and 474877.
Richard.
> _______________________________________________
> support-bugzilla mailing list
> support-...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/support-bugzilla
> PLEASE put support-...@lists.mozilla.org in the To:
> field when you reply.
>