# Filtering tickets that have never been opened **URL:** \ **Category:** Flow Production Tracking\ **Tags:** filter, ticket\ **Created:** [December 16, 2024, 3:32pm UTC](https://community.shotgridsoftware.com/t/filtering-tickets-that-have-never-been-opened/19581 "2024-12-16T15:32:48Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![FrancoisGrosbellet](https://avatars.discourse-cdn.com/v4/letter/f/3d9bf3/32.png) [@FrancoisGrosbellet](https://community.shotgridsoftware.com/u/FrancoisGrosbellet)\ **Post date:** [December 16, 2024, 3:32pm UTC](https://community.shotgridsoftware.com/t/filtering-tickets-that-have-never-been-opened/19581/1 "2024-12-16T15:32:48Z")
Hi everyone, I am looking for a way to filter tickets that I have never opened only - and not tickets that have been updated since the last time opened them. I can’t rely on the `Read\Unread` field, as this would filter tickets that have been updated since I read them. Is there a way to discriminate based on the “never read” information, or a workaround to accomplish it? I am thinking about a solution simple enough so it would not involve the Event Daemon or web hooks to add further information in a custom field of the Ticket entity. Thanks! ---
**Author:** ![Ricardo\_Musch](https://sea1.discourse-cdn.com/shotgunsoftware/user_avatar/community.shotgridsoftware.com/ricardo_musch/32/405_2.png) [@Ricardo\_Musch](https://community.shotgridsoftware.com/u/Ricardo_Musch)\ **Post date:** [December 16, 2024, 6:13pm UTC](https://community.shotgridsoftware.com/t/filtering-tickets-that-have-never-been-opened/19581/2 "2024-12-16T18:13:30Z")
Isn’t this also more workflow related? Are you triaging tickets? maybe all tickets should come in as “new” and then once someone reads it should be set to a different status? ---
**Author:** ![FrancoisGrosbellet](https://avatars.discourse-cdn.com/v4/letter/f/3d9bf3/32.png) [@FrancoisGrosbellet](https://community.shotgridsoftware.com/u/FrancoisGrosbellet)\ **Post date:** [December 17, 2024, 9:25am UTC](https://community.shotgridsoftware.com/t/filtering-tickets-that-have-never-been-opened/19581/3 "2024-12-17T09:25:29Z")
Hi Ricardo, Thank you for your answer. > Isn’t this also more workflow related? I’m not sure what you mean here. > Are you triaging tickets? I have a custom pages with several tabs, each tab filtering tickets on specific needs (tickets that belongs to a specific projects, tickets in a given state, etc.). Many of my colleagues use similar custom pages too. > maybe all tickets should come in as “new” and then once someone reads it should be set to a different status? Yes, but how would the status change from `new` to a different status? This is possible through the Event Daemon or web hooks, but I would like to avoid those solutions if possible. ---
**Author:** ![Ricardo\_Musch](https://sea1.discourse-cdn.com/shotgunsoftware/user_avatar/community.shotgridsoftware.com/ricardo_musch/32/405_2.png) [@Ricardo\_Musch](https://community.shotgridsoftware.com/u/Ricardo_Musch)\ **Post date:** [December 17, 2024, 10:35am UTC](https://community.shotgridsoftware.com/t/filtering-tickets-that-have-never-been-opened/19581/4 "2024-12-17T10:35:38Z")
If you look at a product like Zendesk, it has the following statusses: New Open In progress On hold Resolved Tickets are ‘New’ when they need to be triaged. Once someone reads/triaged them they are “Open”. You could use a similar workflow and potentially combine the “Read/Unread” status to get the desired result. But point being that a ticket should always be triaged once read. ---
**Author:** ![FrancoisGrosbellet](https://avatars.discourse-cdn.com/v4/letter/f/3d9bf3/32.png) [@FrancoisGrosbellet](https://community.shotgridsoftware.com/u/FrancoisGrosbellet)\ **Post date:** [December 17, 2024, 10:59am UTC](https://community.shotgridsoftware.com/t/filtering-tickets-that-have-never-been-opened/19581/5 "2024-12-17T10:59:48Z")
I see. We don’t have strict process to triage our tickets. I’ll bring the topic internally.