Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,258
Community Members
 
Community Events
176
Community Groups

Please support Feature Request "Last-button for queues and customer lists"

Hi everybody.


I have a feature request with Jira about the problem to navigate lists and queues in Jira Servicedesk.

It would be much improved by a "Last" button so you won't have to click the next page one at a time to get to 25 pages later... in our case each page takes 20 seconds to load as well.

Unfortunately it feels slow in gathering support.

I tried to find guidelines prohibiting promoting you own agendas in feature requests in forums, but finding none I guess it is OK? Please correct me kindly if I just missed something.

So please, add your voice to how the pagination in lists could be improved in other ways.

And most importantly, feel free to support the request if you agree:

https://jira.atlassian.com/browse/JSDCLOUD-8495

 

Thank you

Kindly

Jim Melin

1 comment

Jack Brickey Community Leader Oct 17, 2019

Hi @Jim , it is certainly fine to call for support here. That is what communities are for. 🙂

I do see that this would be a nice feature but at the same time curious about the need. It seems problematic that a queue could get so large as to need this. I would drive to keep queues in single digits by refining my queue definitions and more importantly the closure of issues. At the same time I can understand that for a very large organization and/or an agent team that is too small to keep up with the requests the open issues can spiral. This is all just MO of course and seeking to better understand how others use JSD.

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events