JQL Order by Calculated Number Field

[Matthias Herbrich]

Hi,

in our JIRA issues I introduced 4 seperate calculated number fields:

"Factor A": Calculates a Number between 1-5 according to Task Priority

"Factor B": Calculates a number between 1-5 according to Timedifference (Due Date <-> Now)

"Factor C": Calculated a number between 1-5 according to project of task

"Internal Task Priority":  Multiplication of Factor A * Factor B * Factor C

Everything works fine and as excepted.

But in Issue Search, when we using JQL and use "... ORDER BY Internal Task Priority DESC" it sometimes showing wrong order.

For example:

125

100

75

75

100

...

Do you know, why this happens?

Thanks in advance!

[MattS]

I think order by is driven by the Lucene index searcher for a field. In scripted field the value in the Lucene index is only update when an issue is edited. Try sorting as before then edit an issue and see if it's place in the sort order changes

[Chandra Sateesh]

Thats true. One or the other value might have changed during the report. 

[Matthias Herbrich]

But when fired the JQL query I was only logged in Jira user, so while fetching the request nothing could have changed

[Chandra Sateesh]

When does the Internal Task Priority gets updated. During the issue creation or after any other issue operation

[Matthias Herbrich]

Factor A is depending on selected Task Priority (Minor=1 ... Blocker=5). This is selected when creating issue, but theoretically could change after. Factor B (Timedifference) is calculated automatically, so will change every day. Factor C is loaded from a CSV-file where for every project a priority is deposited. Could also change. This means Internal Task Priority could change all the time