> For the complete documentation index, see [llms.txt](https://docs.aqua-cloud.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aqua-cloud.io/documentation/navigation-page/search.md). # Search Easily search project items using keywords, filters, and recent searches. Access results quickly, apply filters, or reset with one click. Shortcut Ctrl+K streamlines navigation. To search for an item at the project level, enter a keyword into the search box and press the 'Enter' key. By default, the system will begin searching for items that meet the specified criteria within the project. If you wish to search for tickets within a specific item type, you may select that type from the dropdown menu prior to initiating the search. Similarly, if you wish to filter results that are of the specific item type, you may select it from the dropdown after results for all types of items have been returned.

Once the items are found, you can open one of them from the pop up by clicking on the title. If you want to check a group of items and apply the filtering next, then click on 'Show on the grid' and the items will be filtered and displayed.

To reset the list on the navigation screen, simply clear the search box by clicking on the cross. For your convenience, we also added a shortcut *Ctrl+K* to trigger search and added 5 recent searched words, making it easier for you to find items in no time. --- # 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.aqua-cloud.io/documentation/navigation-page/search.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.