Recherches récentes
Pas de recherche récente

Brandon Colett
Adhésion le 26 févr. 2022
·
Dernière activité le 20 juil. 2022
Suivis
0
Abonnés
0
Activité totale
6
Votes
4
Abonnement
1
APERÇU DES ACTIVITÉS
BADGES
ARTICLES
PUBLICATIONS
COMMENTAIRES DE LA COMMUNAUTÉ
COMMENTAIRES SUR L’ARTICLE
APERÇU DES ACTIVITÉS
Dernière activité effectuée par Brandon Colett
Brandon Colett a créé une publication,
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
Modification le 20 juil. 2022 · Brandon Colett
33
Abonnés
37
Votes
24
Commentaires