> For the complete documentation index, see [llms.txt](https://docs.testfiesta.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.testfiesta.com/administration-tab/custom-fields/filter-custom-fields.md).

# Filter Custom fields

<details>

<summary>Step 1: Click the filter button</summary>

Locate and click the "Filter" button on the custom fields page

</details>

<figure><img src="/files/JtMnY1qtmHjjHHZN3y7N" alt=""><figcaption></figcaption></figure>

<details>

<summary>Step 2: Select Filter Options</summary>

A window will appear with various filter options. Choose the criteria you want to filter by, such as name, data type, creation date, or data source.

</details>

<figure><img src="/files/1rjaG6IBtOA7yJpEX3p4" alt=""><figcaption></figcaption></figure>

<details>

<summary>Step 3: View Filtered List</summary>

After selecting your filter criteria, the custom fields list will update to show only the items that match your selected filters.

</details>

<figure><img src="/files/TjkePjiFTfjUw79HXS0i" alt=""><figcaption></figcaption></figure>

Congratulations! You've successfully filtered the list. Great job!

Made a mistake when creating your Custom Field, or simply want to change it? Click "Next" to learn how to edit Custom Fields


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.testfiesta.com/administration-tab/custom-fields/filter-custom-fields.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.