Why is ORDER BY considering 27 lower than 3?

[Jon_Fister]

I'm using ORDER BY on a custom field which contains a number to a few decimal places. For some reason it considered 27.xxx to be lower than 3. I think I know why (it counts 27 as 2.7), but why does it do that? Is there a workaround for it?

I'm using this custom field to do prioritisation so 27 being under 3 is a big deal for me.

Here is the JQL:
project = x AND "Calculated Priority" is not EMPTY ORDER BY "Calculated Priority" DESC

[Nic Brough -Adaptavist- · Accepted solution]

What type of field is the "calculated priority"?  Text, number, select etc?

[Jon_Fister]

Seems like a text field (single line). Didn't realise (I didn't create it).

I assume that's why it's out of order, is there a way to convert it to a number field?

[Nic Brough -Adaptavist-]

Yes, if it's text, it'll be sorting by alphanumerics instead of numbers.

You can't convert it, you'll need to add a new one and update whatever is populating it.

[Jon_Fister]

Thanks, at least it's a field that based on calculations from other fields so I won't have to export/reimport data to get my information back.