Open smith4312 opened 9 years ago
Actually should the controller just return all tickets, and let the frontend do the filtering?
We probably don't want to return ALL the tickets since including closed tickets the number could get very huge over time. it might make sense to have 2 API in the controller, one that returns all OPEN tickets for client side filtering, and one that searches even the closed tickets based on some criteria.
The user might want to browse everything, unfiltered. How can he do that if there are a huge number? The solution as far as UI is of course pagination (which could take the form of virtual scrolling if desired). We could do that in the API as well.
On Thu, May 28, 2015 at 3:28 PM smith4312 notifications@github.com wrote:
We probably don't want to return ALL the tickets since including closed tickets the number could get very huge over time. it might make sense to have 2 API in the controller, one that returns all OPEN tickets for client side filtering, and one that searches even the closed tickets based on some criteria.
Reply to this email directly or view it on GitHub https://github.com/smith4312/TAG-Ticket/issues/9#issuecomment-106573379.
Create the main view of TAG Ticket. The default display is a table of active tickets that are assigned to the Agent who has logged in, together with unassigned tickets for his office. The user (the agent) has the ability to change the filter view to also see
This is the main view in the "single page web App"