Search and filtering

The search bar at the top of the ticket list filters by text (subject, content, hashtag) or by structured fields (assignee, queue, status, priority, watchlist). By default the search runs across the Active set of tickets — every open or on-hold ticket in the system — and you can broaden or narrow that set with the scope toggle. You can stack several filters together to narrow the result further or to express alternatives.

Picking a field

The dropdown to the left of the text box decides which field the search applies to. The full set of search modes is:

1. Subject — the ticket subject line.
2. Content — words inside any response on the ticket.
3. Subject + content — matches either; the broad “does this word appear anywhere” search.
4. Hashtag — tickets with a particular hashtag recorded against any response. The text box autocompletes existing hashtags from two characters in.
5. Ticket number — an exact ticket number.
6. Raised by — the originator’s email or name (the person who first opened the ticket).
7. Assigned — the staff member currently assigned. Pick from a list of staff users.
8. Participant — anyone on the ticket (staff, customer, or external participant) by email.
9. Queue — pick from a list of queues you have view permission on.
10. Status — Open / Closed / On hold.
11. Priority — Low / Normal / High / Urgent.
12. Watchlist — pick from your watchlists to filter to tickets in a particular one.

Jumping straight to a ticket

Typing # followed by a six-digit ticket number (e.g. #501379) is a shortcut: Tickiti recognises it as a ticket-number jump and searches across all tickets, regardless of which mode the field is in or which scope you have selected. Use this when a colleague pastes a ticket number to you and you just want to land on it. Selecting Ticket number mode and typing the digits without the # has the same effect.

Stacking filters

The + button to the right of the text box adds a second filter, then a third, and so on (up to five). The × button on a filter removes it; the row collapses and the list refreshes.

How stacked filters combine depends on whether they are the same field or different fields. The rule reads naturally if you put the word “or” between rows on the same field, and the word “and” between rows on different fields:

1. Same field, multiple rows. Each row is an alternative; a ticket needs to match any one of them. So two Priority filters — Urgent and High — together mean “show tickets that are Urgent or High”. Two Assigned filters — me and Frank — mean “assigned to me or to Frank”.
2. Different fields. Each row narrows the result further; a ticket has to satisfy all of them. A Subject filter for marathon combined with a Priority filter for Urgent means “subject contains marathon and priority is Urgent”.

The two rules combine when you mix them. For example, three rows — Priority Urgent, Priority High, Assigned to me — reads as “(Urgent or High) and assigned to me” — the natural “all the urgent or high tickets that are mine right now” query.

The example above uses two Subject filters, so the result is “subject contains marathon OR subject contains warranty” — tickets matching either word would be shown. Here only one ticket matches in the dev data, but the OR logic is what the search applies under the hood.

Search scope

By default, the search bar broadens the set of tickets you are searching across — without it, search would only see whatever your current perspective happens to show, and you would miss tickets that fall outside it. There are three scope options, cycled by clicking the scope button on the left of the search bar:

1. Active (the default) — search every ticket that is not closed (open or on-hold). This is the “normal” setting: most of the time you are looking for a current piece of work and do not care which queue or perspective it is in. Active is itself a built-in perspective; the search just borrows its filter.
2. All — search every ticket you have permission to see, including closed and on-hold ones. Use this when the ticket might be closed (a question about a past resolution, an audit lookup).
3. <current perspective> — search only inside the perspective you are currently viewing (the button shows that perspective’s name). This is the more advanced case: usually a perspective is already a filtered view, and adding a search inside it narrows it further. Useful when you have a custom perspective for a project or queue and want to find one ticket inside it.

Each click of the scope button cycles to the next option and shows a brief toast confirming which scope is now active. The choice is remembered between sessions.

Live updates

Search runs as you type. There is no Search button; the list filters in place after a short debounce. Counts in the perspectives panel do not change — they reflect the unfiltered perspective — but the list itself shows only matching tickets.

Saving a search

The search bar is for ad-hoc, one-off queries; clearing the filters or moving away from the page discards them. If you find yourself running the same combination every day, recreate it as a custom perspective instead — perspectives are saved filter sets with sort order and additional rules.