+assignedbugs listing column sorting shouldn't sort alphabetically for severity

[Brad Bollenbach]

On the +assignedbugs report, e.g.:

  https://launchpad.net/people/motu/+assignedbugs

clicking the column header for severity sorts alphabetically. It should instead sort by the numeric value of the severities.

The same problem appears to exist with other columns on this report, e.g. priority.

[Christian Reis (kiko)]

Doing this right is tricky. The JS column sorter sorts based on the contents of the field, and in this case, the contents are a string. We could add a hidden span before the priority/severity with an ID. Do you have a suggestion as to what ID I should use? Are the dbschema values in the order you want?

[Matthew Paul Thomas (mpt)]

You can't use the same ID for more than one element in the same document. What you could do is move the class= to the <td>, give the classes names that have sort alphabetically the way you want, and tweak the JS to sort first by class= if it exists.

[Brad Bollenbach (bradb)]

On Fri, Sep 16, 2005 at 02:30:04PM -0000, Christian Reis via Malone wrote:
> Public bug report changed:
> https://launchpad.net/malone/bugs/2347
>
> Comment:
> Doing this right is tricky. The JS column sorter sorts based on the contents of
> the field, and in this case, the contents are a string. We could add a hidden
> span before the priority/severity with an ID. Do you have a suggestion as to
> what ID I should use? Are the dbschema values in the order you want?

For the IDs, maybe something like "severity-sortkey",
"priority-sortkey", etc.?

The dbschema values should currently be in a sane order.

Cheers,

--
Brad Bollenbach

[Christian Reis (kiko)]

No longer applies to the current Malone UI.