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.
Do you know, why this happens?
Thanks in advance!
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
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
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hi, everyone! Molly here from the Jira Service Desk Product Marketing Team :). In the spirit of this month's august-challenge, we're sourcing stories of Jira Service Desk activation fro...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs