Zendesk View - Tickets Per Page
Hello,
I would like the option to show 30, 60, or 90 tickets per page, that I can see more tickets per page. Your documentation says you don't allow more than 30. For instance if I get one more ticket above 30, I will constantly be checking page 2. I would like to see things on one page.
When https://support.zendesk.com/hc/en-us/community/posts/4409506839962-Views-Best-Practice talks about this issue, it says spreading things across multiple pages = "Consequently, you are unlikely to review all the results."
Yes, but it goes on to say "If you find you that you routinely only look at a subset of tickets, consider refining the view's conditions to restrict results and simplify the query."
So, the solution to having multiple pages of tickets in one view is to cut a bunch of tickets out of the view and use more views............... this is not how I prefer to manage tickets across multiple views. Essentially, because the ticket status would be the same across most, you're saying we should tag tickets and put them into other views. This is leaving room for us to make the mistake, to not tag properly when these tickets really do not need to be sorted into other views. We just need to see them.
Thank you very much for your support.
[Update - 07/19/22],
I have been seeing your replies, thank you for your posterity. No, there has been no update or reply by Zendesk or the Development Team. I did have luck creating a view with unassigned tickets at the top, and excluding on-hold tickets, which are mainly projects we don't have the time to address anyways. This helped us fit most of our work into one page, but if we were larger or had more than 4 Agents it would still be a problem for us.
I did Google the question to see if any progress was made, and I came across this. There could be a way to return Ticket views using an API. This is above my pay grade but using a cursor based pagination sounds like the thing. According to Zendesk 100 is the true max per page in "Support".
Perhaps you could implement the URL parameter using dashboard customization: https://support.zendesk.com/hc/en-us/articles/4408839321754-Customizing-dashboards-with-URL-parameters
Our plan is Team, so I don't think we are eligible for this feature, and I had no luck trying it in a browser.
https://developer.zendesk.com/documentation/developer-tools/pagination/paginating-through-lists/
To use cursor-based pagination, you must include a page[size] query parameter. Example:
https://example.zendesk.com/api/v2/users.json?page[size]=100-
Just want to second this - Ideally I'd be able to load 900 tickets onto my page - however I'd settle for 90... Would be very helpful.
I might even write a script that does this for us... -
I completely agree!! 30, 60, 90 is not an unrealistic ask, I am strongly in favor of this.
-
I agree with this request. Loading a max of 30 tickets per page is too restrictive.
-
Yes increase it to 60, 90. Such an easy feature to implement, would take a developer 5 minutes...
-
Agree with that, totally.
Zendesk on a 4K Screen means, that 2/3 of your screen remains unused white.
Hello Zendesk, Time of 640*480 is gone, forever.
:-) -
We would love to see this as a feature configurable in Zendesk. Lovely Views (3rdparty) will show more than 30.
-
Yes. I agree that this is a necessary request as well. Has there been any feedback/confirmation from the Zendesk team to confirm if this functionality currently exists or is in progress?
-
Also agreeing here, in theory this shouldn't be too big of a change. Surprised I didn't see older requests for this.
Not all companies are the same, and while 30 tickets for some may be sufficient, other companies may be regularly dealing with way more tickets per agent/view, and it may not be feasible to filter this into multiple views. Giving admins an option to adjust this based on what makes the most sense for their team would be ideal.
-
I support a development change to increase the number of tickets in a view. 30 is restrictive for my company, as we receive thousands of tickets annually and we ever-so-often have turnover of agents. Having to reassign tickets from a departing agent to a new agent can be time consuming if the departing agent has several hundred actionable tickets assigned to them.
-
Strongly agree with this.
-
Any updates on this ? I will start developing a greasemonkey script this weekend as I am tired of this function not being widely available
-
If possible, would you like to share your result, Mr, Baker? It could be worth a bottle or two of a drink of your choice.
-
Any update from the Zendesk team on this?
-
Would be most helpful and beneficial.
댓글을 남기려면 로그인하세요.
14 댓글