nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Custom Number Field not sorting correctly

Melanie Wu

I have a Custom Number Field with the Search Template set to use the Number Searcher. I have re-indexed several times, however, the numbers still don't sort in order from smallest to largest or vice versa. The numbers are whole integers. The instance where I am having the problem is set up with the Data Center configuration. Our other instance where setting the correct search template and reindexing solved the problem is just a regular server set up. Are there any known issues with Data Center regarding this? Or anything I can look into regarding how our DC is set up?

Unfortunately, I can't provide any screenshots since these instances are set up on an isolated network.

Thanks,

Mel

Accepted answers

Melanie Wu

Fixed it. Sort of. I initiated the re-index directly on a specific node and it fixed the numbering issue. Unfortunately, it caused the other node to be corrupted but that is a different issue. So I guess it was Data Center related.

All comments

Nic Brough -Adaptavist-

Could you just explain how the numbers are sorting? (In lieu of screenshots)

e.g. given 1, 4, 12, 16, 105, when you run JQL like "my-number-field is not empty order by my-number-field ASC", what order do you get out?

Melanie Wu

I have numbers from 2-229. The first ten numbers when I sort in ascending are:

3, 6, 12, 2, 4, 5, 16, 8, 9, 10

Descending:

229, 223, 221, 228, 220, 227, 219, 226, 212, 210

Some background:

I have a scripted field (DPM Weight) that reads several other list fields. Each option for those fields are assigned a weight, and the scripted field checks the values and totals the corresponding weights. The DPM Weight field sorts just fine with the numeric values. The DPM field ( the number field that is not sorting correctly) gets populated by a listener. If x field option is y, then DPM is set to 1. All else gets populated with 2-N dictated by a JQL string and sort order.

I gave the customer the JQL string to use to view the correct sort order as a short term solution, but they keep complaining that they should be able to sort off the DPM field.

Sorry if this background info was useless and only served to cause more confusion...

Nic Brough -Adaptavist-

Hmm. I can't see any pattern to that, which suggests to me that Jira is not seeing the contents as numbers.

What exactly is the field type of the field?

Melanie Wu

It is a "Number Field"

Melanie Wu

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server