> 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/items/defects-management/defects.md). # Defects Bugs or defects in software refer to anomalies or imperfections within a digital product that cause it to behave unexpectedly, incorrectly, or inadequately. These issues can occur at any stage of the software development lifecycle and can take various forms. In aqua, you can file the defect from multiple places. The most common one is from the Navigation page. Hover on the 'Add new' button and select the 'Defect' option from the menu.

Once you click on the 'Defect', you will be navigated to the new defect page where you can provide all necessary details.

You can also create a defect from a navigation tree, simply select a project or a folder and then click on the plus and select the 'Defect' option. from the menu

There is also an option to create a defect as a dependent item from any item page. Just select this option from the ribbon under the 'Create dependent item' group.

--- # 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.aqua-cloud.io/documentation/items/defects-management/defects.md?ask=&goal= ``` `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.