I would like to order issues by "remaining time" defined by SLA. The problem is for breached issues.
ID | remaining time
ticket #2 | 0:40
ticket #1 | 1:35
ticket #3 | -0:30
Why the ticket #3 is not in first position ?
Thank for your help,
Issues are ranked by time remaining for SLA fields only when the SLA is ongoing. Any completed issues are ranked last. This enables a Queue to be sorted by an SLA field and have issues with an ongoing SLA always appear first.
If you are seeing some unexpected behaviour in how SLA fields are ordered on a Queue could you paste a screenshot of the Queue in edit mode with the 'Tickets to show' area in 'Advanced' mode (so the underlying JQL is visible) - I'll have a look and help you get to the bottom of it.
It seems like it is a bug behaviour which is already been report in here: https://jira.atlassian.com/browse/JSD-206
Please feel free to comment and add yourself as watcher in order to receive any latest updates from the developer and feedback from other user that is facing the same issue.
For more information on how Atlassian implements bug fixes: http://confluence.atlassian.com/display/JIRA/Bug+Fixing+Policy?utm_source=support
Thanks for the information. Don't be able to sort by SLA correctly kill this feature of Service Helpdesk.
I want my team to deal with issue by "time remaining" order. I will have to make two blocks in dashboard : one for breached SLA, one for non-breached SLA :-/
I watch and put a vote one the issue.
The Jira Service Desk marketing team is working on a guide to help new Atlassian customers switch from email to JSD and we'd love to hear from you! Please share: - What made you realize that i...
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