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!

Yes please, very basic and needed option if you ask me.

We've been really astonished, that this feature is NOT available. Our agents really want to have this feature, because they're used to it from other products. Please implement it.

If I use the JIRA view of my tickets then I can do the sorting, but unfortunately the SLA remaining time will not be shown.
So please fix this in Jira Service Desk, thanks.

Oh wow this is NOT avail? I am constantly amazed at what key functionality Service Desk lacks.

Hi All,

Yes we'll like an update on this as well. We've recently migrated from SCSM over to JIRA Service Desk, and for agents, this is a pretty essential function.

Please advise.

Thanks,

• Jana Squires

Hi all!

Is there a workaround for this issue? I dont think this is due to be fixed anytime soon..?

we need this for a efficient service desk ... like in the filters view ....

Would be great to see this. It is a right pain and I've ended up creating dashboards to workaround it.

*1 for Michele's comment

Adding my supporting comment from JSD 2190. As an agent I would like to have the ability to sort by clicking on the column in a queue, which is then only local to my login and not change anything for anyone else.

(As only admin can choose how tickets are ordered and once that's set the admin changing it would change it for all Agents).

For instance be able to click on the Reporter field to group in ascending order, so I can easily and quickly see without having to go into JIRA and create a JQL search all of one reporters tickets. Or sort all the tickets by created date to quickly see which tickets came in first or last. Or sort by priority so I can see Highest at the top or Lowest. Having this flexibility would make me more efficient.

Any ideas when this will be implemented?

+ 1