What I was thinking was along this line: right now you have one table on the web app for ALL active which includes active and resolved tickets. Maybe create a seperate table for resolved tickets. Then when someone sets the ticket status to resolved, it triggers an automation that moves the ticket off of the all active table and onto a seperate Resolved table. That way, the analysts can sort through tickets that need to be done or are in the process of being worked on, without having to fish through the list of resolved tickets as well.
