# Step 2: Configuring Jira connection

> Configure a Jira Server or Jira Cloud connection in Test Manager, including authentication, server URL, and defect type settings.

A Jira connection links a Test Manager project to your Jira instance.

## Setting up a Jira connection

The connection is created in Test Manager from Project Settings > Integration, using the connection type that matches your Jira product.

### Context

* All the objects that you create in Test Manager have the identity of the Jira user used for this connection.
* For Jira Data Center, you set up a connection for **Jira Server**. For Jira Cloud, you set up a connection for **Jira Cloud**.

### Prerequisites

A Test Manager administrator account.

### Steps

1. Log in to Test Manager as an administrator.
2. Open your project.
3. Navigate to **Project Settings** > **Integration**.
4. Select **New Connection** and select either **Jira Server** (Jira Data Center), or **Jira Cloud**.
   * (For Cloud Commercial and Cloud Public Sector only) You can select between **Basic Authentication** or **OAuth** as authentication type.
   * (For Cloud Dedicated only) The default authentication type used is **Basic Authentication**. You can't change the authentication type.
5. Configure the following connection settings:
   * **Name**: Enter a name for your Jira connection.
   * **Description** (Optional): Add a description for reference.
   * **Server URL**: Add the Jira server URL. This is the URL of the server that exposes the Jira REST API. It is usually identical to the URL you navigate to when using Jira through your browser. For example: `https://company-name.atlassian.net`.
   * **Web URL** (Optional): Enter the URL of the Jira REST API in case the Jira REST API is not hosted under the same URL as the web UI.
   * **User**: The username you use to authenticate to the Jira API.
   * **Password** (Jira Server only): The password you use to authenticate to the Jira API.
   * **API Token** (Jira Cloud only): [Generate an API token](https://id.atlassian.com/manage-profile/security/api-tokens). For more information on Atlassian API tokens, see [Manage API tokens for your Atlassian account](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/).
   * **Defect Type**: Specify the Jira object-type to be used for defects. Usually, that is a bug. To disable defect integration for this connection, select **None**.
   * **Project Key**: Enter the project key from Jira which refers to the project you want to integrate.

   ![Jira connection settings form in Test Manager](https://dev-assets.cms.uipath.com/assets/images/test-manager/test-manager-docs-image-126859-d77939a1-5e801b73.webp)
6. Select **Save**.
7. Select the connection to expand the panel and copy the **API Key** for later use.

### Result

The Jira connection is saved in Test Manager, and you have the API Key to use when configuring the Jira project.

## Editing a Jira connection

Editing a connection changes the settings of an existing Jira connection, such as the server URL or the credentials.

### Prerequisites

* A Test Manager administrator account.
* An existing Jira connection.

### Steps

1. Log in to Test Manager as an administrator.
2. Open your project.
3. Navigate to **Project Settings** > **Integration**.
4. Select a Jira connection to expand the panel.
5. Select **Edit** to configure the connection.
6. Select **Save** to confirm changes.

### Result

The Jira connection settings are updated and the changes are saved.

## Deleting a Jira connection

Deleting a connection removes it together with its associated requirements.

### Prerequisites

An existing Jira connection.

### Steps

1. Log in to Test Manager as an administrator.
2. Open your project.
3. Navigate to **Project Settings** > **Integration**.
4. Select a Jira connection to expand the panel.
5. Select **Delete** to remove the connection.
6. Select **OK** to confirm.

### Result

The Jira connection and its associated requirements are removed from Test Manager.