> For the complete documentation index, see [llms.txt](https://docs.enate.net/enate-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/enate-help/work-manager/work-manager/quickfind/quickfind-searches-with-custom-data-fields.md).
# Quickfind Searches with Custom Data Fields
You can search for work items and their emails using focussed ‘search this value in this field’ on the work item. This is achieved by prepending the search with predefined search code. Before typing anything into Quickfind, the dropdown displays all short codes available in the system, and the field they relate to.
To search against a field, enter the short code and the desired value e.g. hq:Laptop
This will return work item (Ticket/Case/Action) and communication results where this field has this value:
### Using Quotes to search for entire phrases
You can put quote marks around your search value to search for an entire phrase as the field value you want to find e.g.: bn:“entire phrase”
You can also use this approach to search for phrases with general free text searching, i.e. even when you are *not* searching against a custom field with a prepended short code.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.enate.net/enate-help/work-manager/work-manager/quickfind/quickfind-searches-with-custom-data-fields.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.