> 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/option-to-hide-enclosures.md).
# Option to hide enclosures
To keep defect tracking clean and avoid confusion—especially for teams using **Jira sync**—you can now choose to **disable adding multiple enclosures** in a project.
This setting is particularly useful because Jira supports syncing **only one enclosure** (the *description* field). Disabling additional enclosures ensures smoother sync and a consistent experience across both systems.
#### ✅ How to Disable Adding Enclosures
* **Navigate to your project** in the left-hand menu.
* Click the **three-dot menu** next to your project name.
* Go to **Project configuration → Settings**.
* Under the **Defect** section, check the box labeled **“Disable adding enclosures.”**
* Click **Save** to apply the change.
Once enabled, the option to add new enclosures (e.g., *Description*, *Note*, *Resolution*) will be hidden when creating or editing a defect.
#### 🔄 What Happens After Disabling
* **New defects**: The “Add Enclosure” group will no longer appear on the ribbon.
* **Existing defects**: Any enclosures already added will remain visible and editable.
* However, if you delete an existing enclosure, you **won’t be able to add a new one** unless you re-enable the setting.
---
# 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/defects/option-to-hide-enclosures.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.
