> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/integrations-in-avo-assure/test-management/jira-integration/auto-defect-creation/template-creation.md).
# Creating Template
**To create template for auto defect creation, perform the following actions:**
1. From the **Jira Project** dropdown, select the **required Jira project.**
2. Choose **Issue Type** as **Bug** from dropdown drop down.
3. Enter **Description** in the **Description textbox**
4. Enter **Summary** in the **Summary textbox** and select **Priority** from the Priority dropdown
5. Enter **Environment** in Environment textbox.
{% hint style="info" %}
**Note:** If the user wants a more detailed defect template, they can click Select Fields button in the Create Defect Template window and choose the required options to add fields in the defect fields area.
{% endhint %}
6. Click **Save** button to save the Defect Template .
{% hint style="info" %}
Note: Once the defect template is created, the user cannot edit the fields.
{% endhint %}
---
# 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.avoautomation.com/avo-assure/integrations-in-avo-assure/test-management/jira-integration/auto-defect-creation/template-creation.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.
