# Filtering and searching ticket history

The Ticket History page lets you search, sort, and filter. Here is how to use it for the questions your team asks most.

## Searching

The **Search** box matches by **user ID** or **ticket ID**.

* To find a member's tickets, paste their Discord user ID.
* To find one ticket, type its ticket ID.

Results update a moment after you stop typing.

## Common views

### Tickets opened by one member

Paste the member's Discord user ID into the **Search** box.

### What one staff member handled this week

* Add the **Ticket Moderator** filter and pick the staff member.
* Add the **Date Range** filter and set it to Last 7 Days.

### Closed tickets with a low rating

* Set **Status** to Closed Tickets Only.
* Add the **Ticket Rating** filter and pick 1 and 2 stars.

Ticket ratings are a <i class="fa-crown">:crown:</i> Premium feature. On a free server tickets have no rating, so this filter returns nothing.

### The oldest tickets still open

* Set **Status** to Open Tickets Only.
* Set **Sort** to "Open Time, Oldest First".

The first results are your oldest open tickets, which usually need attention first.

### What your team closed last week

* Set **Status** to Closed Tickets Only.
* Add the **Date Range** filter and set it to Last 7 Days.

The ticket counter and the table give you a snapshot for the week. For charts and totals over time, use the [Statistics](/docs/statistics/the-statistics-page.md) page (<i class="fa-crown">:crown:</i> Premium).

## Filtering by more than one staff member

The **Ticket Moderator** filter accepts more than one person. Add the first staff member, then add another, and so on. The list then shows tickets that any of the selected staff acted on.

If a staff member is not in the list, type their user ID into the box at the top of the filter and click **Add**.

## Reset Filters

A **Reset Filters** button appears next to the filters once any filter is set. It clears every filter back to its default.

## Notes

* The list is paginated, so large servers do not load every ticket at once.
* The ticket counter at the top reflects the filters you have set, not always the full total.
* A very wide date range, such as All Time, can take a moment to load on a large server.

## Related

{% content-ref url="/pages/EXi2VYmzaYjnpkXRHAAR" %}
[Browsing open and recent tickets](/docs/tickets-history/browsing-tickets.md)
{% endcontent-ref %}

{% content-ref url="/pages/FbKCvUVzdQTcW1xoif1r" %}
[The Statistics page](/docs/statistics/the-statistics-page.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ticketking.xyz/docs/tickets-history/filtering-and-searching.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.