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.
On Fri, Sep 16, 2005 at 02:30:04PM -0000, Christian Reis via Malone wrote: /launchpad. net/malone/ bugs/2347
> Public bug report changed:
> https:/
>
> 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