Sorting is done via indexing (Lucene Index) in JIRA. Since time changes every second it is hard to index, so we are indexing the target date. However if the issue is in paused times, the same problem re-occurs.
We had some implementation to re-calculate and re-index within recent versions of Time to SLA.
Are you using the latest release of Time to SLA add on? If not could you please upgrade?
Thanks for your response, we are using the last version 5.18.0 of TTS (lastest compatible with our JIRA v6.3.12).
As for the indexing by target date I guess it makes the sorting not possible for the overdue SLA, but the ones in "StillHaveTime" why is it not working ? (cf screenshots - one in a sorting asc, and the other in desc on TTS column.
Sorry for the late response.
Generally if the issue is in a paused status, then the target date changes by time.
However, both should work with latest version. Could you please check those issues using SLA Report? That report will give exact date and time values (SLA Target Date).
Last, I think this issue needs to be investigated with a more detailed way. So it would be good to raise an issue with these details. Could you please do that so that you'll get notified about the progress.
Hello there Cloud Community members! Today, we’re thrilled to announce Jira Service Management, the next generation of Jira Service Desk. Jira Service Management touts advancements in IT service ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events