> 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/creating-a-defect-from-a-test-execution.md). # Creating a defect from a test execution Create defects directly from manual test executions - auto-link cases, transfer relevant execution data, and track dependencies for seamless issue management and efficient retesting. While executing a manual test case, you can create a new defect by clicking on the 'New Defect' button from the ribbon. You can also click on the info bar, which promts you to file a defect as soon as you mark the step as blocked or failed.

A new tab will open and you are able to document and save your defect. Please make sure you have pop-ups allowed. The information from the execution is automatically transferred and the test case as well as the execution are linked to the defect via a dependency. In addition, information from selection fields with shared value sets as well as text fields are also transferred, provided that these are named the same in the test case and defect.

After saving the defect, the ticket will be added as a dependency with a relation 'detected by' type and connection to the corresponding test execution where it was found. Later when you need to retest the defect, from the Defect tab you can select a bug ticket and select from the menu 'Find dependent' => Test cases

And it will show you the test case(s) that you need to re-run.

--- # 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/items/defects-management/creating-a-defect-from-a-test-execution.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.