Tickets Fixed Ticket Queue: Number of Ticket Count messed up (2 Issues)

First Issue: In the Options setting it is set that the Queue should only show 20 tickets per page. So the pagination should start when the 21st is created.



...but on the Ticket Queue Page it shows all tickets (22) and no pagination, plus there is a...

Second Issue: The counting is messed up...

What kind of tickets did you have on that page (i.e. assigned, deleted, etc)?

Bare in mind, assigned tickets function like sticky threads. They don't count towards the pagination limit.

I don't really understand why the status of the ticket matters. I just would want to see the actual number displayed in the page that are there MINUS any deleted tickets MINUS filtered out tickets but of course with any type of tickets no matter what status they have. Why so complicated?

This is still messed up, especially when you have multiple pages... how could that be possible that you show 1-21 on the first page and then 21-23 on the second page... that's messed up.

This is because of how tickets and assigned tickets are counted. It gets kind of fiddly when you take in to account that some people may see some tickets and others won't see them.

I'll see what I can do.

Hmmm I can see every ticket because I am the admin with full permissions and still the numbers are messed up

Hey,

when a user has no permission to view others' tickets, they should not be shown in the ticket count. For example we have a category with 2 tickets, when directly linking to it a user with no permission to view others' tickets can see:

Showing tickets 1 to 0 of 2

That should not be the case

Hey,

I've sorted resolved tickets by their last message date or start date, but it seems like it does not work when there's value like "today" or "yesterday":

Yeah, there’s some issues with the current handling of this (see the other open issues).

I’ve redoing this layer of tickets in 1.6.0 but it’s pretty substantial so it’s not something that can be done with a few lines. I’m hoping to open up 1.6.0 to some beta testing in the next week or so.

I believe this is resolved in 1.6.0 now. In my testing, it looks and works a lot better now.