Thanks Robbie

I can confirm that this feature is available in version 8.6.

Is this available in 8.6 ?

We are working on this.

@thealexauer1 Thats great! Thanks for the good news.

It will come in the next release:

https://confluence.atlassian.com/jiracore/preparing-for-jira-8-6-976172765.html

+1

I can´t understand why this is not available yet?! This is such "simple" function every table should have...

@msingh (Mandeep Singh) If you could put this issue, together with 

• https://jira.atlassian.com/browse/JSDCLOUD-298
• https://jira.atlassian.com/browse/JSDCLOUD-357
• https://jira.atlassian.com/browse/JSDCLOUD-4957
• https://jira.atlassian.com/browse/JSDCLOUD-4580

IN DEVELOPMENT, then you'd stop losing another Service Desk customer some time in the next few weeks...

This should have been in the product from day 1, yet the portal is still missing basic functionality, and everyone keeps suggesting additional marketplace apps that are hard if not impossible to justify to management cost-wise...

Under consideration in short term roadmap.

+1. Really don't understand why this is not an "out of the box" functionality !

Waiting for such a long time to get that feature implemented

+1 our customers are requesting this function. Please implement this

+1

+1 waiting it

+1 - I mean you already have it in the search results that you can sort on any column.  Why would this be any harder??

+1 

+1

How many voets are required.This requet is here for  5years already.

+1

Our Agents really need that for efficient daily business

+1

+1

+!

+1

Cmon bring it to on-premise soon. It's still a huge minus.

+1

Come on, Atlassian, it's 2018, almost 2019. All modern UI grids allow that. Please get this out to users ASAP. While at it, make the column headers also have ability to filter, aka quick search.  I have no ability to explain to highly technical IT users and programmers how come this feature is not available from the box on day one of Jira Service Desk. That is simply unreasonable, and it's a huge minus to those who have to work the queues all day every day.

I would love to see this feature, especially when it comes to the 'Assigned to me' queue. When you have multiple people working out of the same project, each one should be able to sort and filter this queue to their own liking.

Since it is available on Cloud version, I can believe this update will be also available on on-premise version???

Today this feature was released for the cloud version. We will have any traction for JIRA Service Desk Server?

Most of our tickets need longer time to get resolved. We end up with long queues, it is very useful to offer our agents to sort the queue depending on a shown field, with out this feature,  queues are useless and agents end up searching issues using filters then using the issue list view and sort the result the way they want. Please consider this.

Added my vote too... waiting this basic feature impatiently

I just put my vote in. Our Que is getting pretty big and our product manager would love to see this. 

Coincidentally, in Cloud just today there was a survey pop-up when I went into Queues for one of my project. The survey was to gain feedback on top 5 improvements I would like to see. I was pleased to see at the top was this request. It was certainly my #1 vote. So, at least for Cloud users, we might see this in the near future.

Alternatively Queues for Jira Service Desk from Deviniti provides this functionality inexpensively.  Currently it doesn't support display of Insight Custom Fields (if you're using Insight) but they tell me that should be fixed soon.

Hi Everyone -

I started watching this ticket because it would be nice to have, but I've given up on their ServiceDesk project page all together at this point. The Queues feature is really just a list of filters. You can extract the logic from the queues to generate filters and get the full functionality you're looking for. Although inconvenient, we can stop sitting around tapping our feet and letting the rage begin to boil over into the comments fields of this ticket and instead use the existing feature available to us in standard Jira. 

Can we have an update from Atlassian on this issue please. The issue status is currently "GATHERING INTEREST" which I think is pretty clear with the number of votes and the simplicity of the request (understandably not the simplicity of the implementation or it would have been done long ago).

Also that GATHERING INTEREST seems a bit redundant for simple features like this. There is hardly a data table on the internet that does not have sorting and this is a data table. 

There is a lot of effort lately in visual theme upgrades within Jira and Confluence etc and nice as that is, there are basic functional requirements that we would expect to have higher priority than look and feel. (like this one)

Can we get an update on this issue and if at all possible some ETA indication?

Thanks

The lack of sorting on the fly is causing a lot of churn and users are starting to maintain an excel file offline. We really need this implemented soon.

Please implement this. The fact that we have to ask for this basic functionality is absurd. So instead of using Service Desk, my agents need to create their own custom filters and sort there. What a joke.

This is a basic requirement for ITSM queue management. I dont understand how this is not a standard functionality.

I was stunned to see this was a feature only under consideration. Use case: we have a queue for 'new hire requests' and I want to sort by Due Date (the date the resource is starting) so we can at-a-glance see who's starting. Right now I've got to sort through dates manually. To add a sort so I can sort ascending and lock that in as the queue view for everyone would be a huge time saver. Can't believe this is under debate - it's basic UI. 

a must-have feature.

The fact that this feature has been request since 2014 is disheartening as a platform. This is a basic help desk feature and makes it hard to fight to keep Jira Service Desk with missing features like this one while help desk staff request this all the time. 

Please include this is really needed.

Pretty basic this but would be a very effective feature.

Any update ? This is a core feature of many service desk tools

This feature can be very useful. 

I will appreciate it if you add it.

Please include!  We have lots of votes over here!

How hard can it be to decide to include this basic functionality that is available in other Jira screens...

Need this–people have been asking for years

Attempting to implement Service Desk for my support team and not having this functionality is a near-deal breaker for them...

Need this

Need this one.

We have been waiting for 3 years for this feature to arrive) ability to sort table.

How do you sleep at nights?)

@Fredrik Jahr, see here for that one: JSDSERVER-357
Same story anyway.

Completely miss understood this add-on. I thought it was an add-on for the customer interface. 

Ignore my comments. 

Also, does this InTENSO add-on support the following add-on: https://marketplace.atlassian.com/plugins/com.refinedwiki.jira.servicedesk.refinedtheme/server/overview

If not, I think you realise the problem working in multiple layers of add-ons.

Feels weird to have add-on to an add-on.

I understand InTENSO are simply responding to a demand in the marketplace, I can scarcely fault them for that, but the notion of paying extra for absolutely basic functionality is truly galling when we consider the cost we're already paying for Jira Service Desk licenses.

It feels like I've leased a car but it is missing a gear-stick. And there is someone that leases gear-sticks, with a stall in the very same marketplace, that just happens to be able to assist with this deficiency.  It is amazing how quickly the TCO seems to climb when third-party add-ons are needed to cover the most basic features. 

EDIT: To be fair it does seem that the 'Queues for Jira Service Desk' app offers more than just being able to sort queues.

@Jorge Lopez, @Paolo Bellei, @Yifa Bavlit, and all. I want to proudly announce that our Queues for Jira Service Desk app solves this problem. It is available for both Jira Server and Jira Cloud. Please check it on the Marketplace.

If you have any question, don’t hesitate to e-mail us at contact@intenso.support

https://marketplace.atlassian.com/plugins/com.intenso.jira.queues-extension/server/overview

I am wondering if this issue is even being monitored.  I dont see any actions, releases scheduled for this issue since 2014.  All I see is the comments we post.  This is unacceptable for this type of service.

I find it hard to think which other issue could have an [importance]/[development time] ratio higher han this one for JSD. It's amazing that it's still open.

We really need this. Scaling JSD for the whole enterprise lays on this capability. 

I would hate to move to a different product... 

@Atlassian I'm with Frederik, this would be really cool if you can make this possible.

@Atlassian – Please, this is such a important feature. All our customers want this feature. It's easy to implement, and should definitely be added to the next release.

Thanks!

Yep, same here, as Vesa is saying - that's more or less the first thing my team asked about. This should be basic functionality, it's intuitively wanted.

@Atlassian  - please, consider implementing this feature in the next releases. Thanks in advance!

Yep, same here, as Vesa is saying - that's more or less the first thing my team asked about. This should be basic functionality, it's intuitively wanted.

@Atlassian  - please, consider implementing this feature in the next releases. Thanks in advance!

I completely agree with the previous comment. This should be basic functionality. This was the first thing our agents asked after using the desk for couple of days...

@ATLASSIAN TEAM - Comeon...This is not something that should be dependent on the number of votes it receives. It is a fundamental functionality from a User Experience(Agents) point of view that should be introduced ASAP. We just implemented Service Desk within our organization and within a month of use, it's the first thing agents have been asking to have...<hint...hint>...Looking forward to a fix soon...

The fact you are unable to sort a queue by date is hard to comprehend.

@Danny Archibald I think you're confusing being forced to use things a certain way, with what an ITSM tool should provide in terms of flexibility.

Your use case might be valid for simple workflows and simpler service catalogues. Defining a different queue for various Asc/Desc ordering of fields is not only a painful process when dealing with multiple fields, but also a very static process when adding/removing fields.

Also the width of the queues list is fixed, so don't even try setting up a proper description for a custom queue. "In Progress due in 24 H ASC" would get trimmed to "In Progress due in ...". Good luck understanding which queue is which!

You mentioned filters, but those do not update automatically, those are some very static search results. So that defeats the purpose of the live queue, and sets you back to looking for emails or refreshing screens every few minutes. Also favorite filters are not even placed where it would make sense, but instead Atlasssian is imposing its own defined filters, which when talking about a ticketing system, don't make much sense either (why would I want to know issues reported by me as a technician, or recently viewed, or even done/resolved?).

On the other hand, it's exactly filters I'd use if I'd really want to have a talk with a technician about his/her issues, and even more, create dashboards/reports based on, not queues.

Regardless the use case, providing flexibility is what made Atlassian products great comparing to others. Not implementing something rather trivial like this live sorting (for customer portal too, but that's another story), in over 3 years since the request has been made, only damages Atlassian's image and our trust in them. Due to similar trivial improvements that Atlassian is refusing to implement, our company is actually looking at other vendors, for all its Atlassian products (we have Jira, Confluence, BitBucket, FishEye, Crucible and ServiceDesk + over 20 plugins just to provide workarounds and some decent-ish reporting), seeing Atlassian is not a reliable vendor, without a proper transparent roadmap (excluding ofc. strategic features).

Hey all,

I've been getting the comments on this since I started using JIRA and wanted to have this functionality.  I thought I'd put my two cents in after using JIRA Service Desk for several months now, and have decided I don't think they should make this change.

Here's how I see it based on being the I.T. Manager over our Service Desk for a few months.

1. The main queue's are set in stone.  Because of not being able to sort these, you can communicate easier about what's there because you are all seeing the same thing all the time.
2. Each user can set up filters to see whatever they want and be able to sort the columns in those.  Filters can be set up to mimic the main queue's.  Anyone can set up filters and share them out to the entire team.

So with all that in mind, I feel it makes sense to have things the way they are.  You have a standard view in the main queues that the admin/manager sets up to match how they want their teams workflow/priorities to go, and all the techs have the ability to create the filters they want/need with sorting functions.

For instance, our main queue's are set up to show newest on top, and also "user" tickets on top, "internal" tickets on the bottom.  If sorting were possible, then anytime you go look at another techs screen with the same queue up, then it might look different, instead of say asking them to pull up the queue and it looks the same as the one you are looking at.

Just my thoughts on it.  I thought it was crazy that this functionality wasn't there when we first started using this, but now it makes more sense to me.

this is a base functionality, please add

You cannot have a support system for enterprise without basic functionality like this one.

How is this not already a thing? 

Need this!! No Question. This is standard for every ticket system!

I just voted for this functionality, because it is such an important function to have available. It would make it a lot friendlier for myself and fellow co-workers. PLEASE!!!!!

Come on Atlassian.  This is a must have!

THE thing that stops me using JIRA Service Desk, run away when I see this in 2018..

It boggles the mind that this sort of feature even needs to be requested - surely this is a basic usability feature when dealing with tabular results?  The fact that this still hasn't been implemented more than three years after this case was created is a little alarming.

We would really like to see this functionality

This will ultimately make the cut, but dont let that stop you from using the service desk.

Lack of this feature is why partially responsible why we're still consider wether or not to move to JIRA ServiceDesk.

I'd love to see this. Using an issue filter is a great workaround, but I'd like to try and keep agents working inside queues and not having to leave the ServiceDesk project to view their work.

Its interesting to see the functionality on Jira, but not on JIRA help desk.  This should have been seamless as it was a duplication of standard functionality when JIRA service desk was built. If it exist in Straight Jira, then it should flow to JIRA service desk.

Please get this done.  If it has already been done, please let me know when I can set that functionality.

How is this honestly not a feature built in already. I am finding more and more that switching to JIRA Service Desk to be a mistake. Absolutely inexcusable to charge so much for a (I feel) Beta product that depends too highly on 3rd Party Add-ons. 

This is basic functionality, please allow sorting on the fly in the queues.

Not a good work around but one nonetheless - I have created a dashboard for the team's queues w/ filters. It is a generic dashboard where the filters equate to assignee=current_user and there is also a filter to show unassigned which equates to issues that need to be triaged and assigned.

Hi, there.

I need it very very very much!

Very basic and a must!