# Manual Defect Creation

In Avo Assure, manual defect creation is the process where a user identifies and logs a defect into the system manually, providing details such as the issue description, severity, and related test information. It allows user to report issues that occur during test execution when automatic defect creation is not configured, ensuring proper tracking and resolution of software defects.

## Prerequisites

User must ensure the following requirements are fulfilled before proceeding with Jira integration in Avo Assure. &#x20;

### Cloud Authentication Prerequisites

#### For the cloud authentication, here are the prerequisites:

* **Jira Credentials:** Keep Jira login credentials ready to use during authentication.
* **Jira API token:** Generate the Jira API token and store it securely for use during authentication.
* **Jira Instance URL:** Ensure the Jira URL is correct and accessible to use during authentication.
* **Avo Integrator:** Ensure the Avo Integrator extension is downloaded in the browser. This required for Login, Mapping, and Execution Configuration in Avo Assure.

{% hint style="info" %}
**Note:** To integrate with Jira without using the Avo Assure Client, user can install the Avo Integrator Extension in user's browser and perform the integration. For installation steps, refer to [Avo Integrator.](/avo-assure/integrations-in-avo-assure/avo-integrator-extension.md)
{% endhint %}

* **Avo Assure Client:** Ensure Avo Assure client is connected and it's required for executing the test case and update status in Jir&#x61;**.**

### Data Center Authentication Prerequisites

#### For the data center authentication, here are the prerequisites:

* **Username:** Ensure the Jira Username is ready to use during authentication.
* **PAT token:** Generate the PAT (Personal Access token) token and store it securely for use during integration.
* **URL for Jira instance:**  Ensure the Jira URL is correct and accessible to use during authentication.
* **Avo Integrator:** Ensure the Avo Integrator extension is downloaded in the browser. This required for Login, Mapping, and Execution Configuration in Avo Assure.

{% hint style="info" %}
**Note:** To integrate with Jira without using the Avo Assure Client, user can install the Avo Integrator Extension in user's browser and perform the integration. For installation steps, refer to [Avo Integrator.](/avo-assure/integrations-in-avo-assure/avo-integrator-extension.md)
{% endhint %}

* **Avo Assure Client:** Ensure Avo Assure client is connected and it's required for executing the test case and update status in Jir&#x61;**.**

### This document Includes:&#x20;

1. [Authenticating Jira](/avo-assure/integrations-in-avo-assure/test-management/jira-integration/manual-defect-creation/authenticating-jira.md)
2. [Mapping Test Cases](/avo-assure/integrations-in-avo-assure/test-management/jira-integration/manual-defect-creation/mapping-test-cases.md)
3. [Create Defect Through Reports](/avo-assure/integrations-in-avo-assure/test-management/jira-integration/manual-defect-creation/create-defect-through-reports.md)
4. [View Manually Created Defect in Jira](/avo-assure/integrations-in-avo-assure/test-management/jira-integration/manual-defect-creation/view-manually-created-defect-in-jira.md)


---

# Agent Instructions: 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:

```
GET https://docs.avoautomation.com/avo-assure/integrations-in-avo-assure/test-management/jira-integration/manual-defect-creation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
