# Troubleshooting the Jira integration

> Solutions for connectivity and configuration issues when connecting Jira Server or Jira Cloud to Test Manager, including API key connection timeouts.

## Connect timed out when adding the API key to Jira Server

### Solution

If the Jira Server plugin displays `Given configuration is invalid. Please check Server Url and API Key. org.apache.http.conn.ConnectTimeoutException: Connect to cloud.uipath.com:443 ... failed: Connect timed out`, the API key is rarely the cause. This error most often means the Jira Server host's outbound firewall or proxy is blocking port 443 to `cloud.uipath.com`.

To diagnose and resolve the issue:

1. From the Jira Server host, verify outbound connectivity to `cloud.uipath.com` on port 443, using `curl -v --connect-timeout 10 https://cloud.uipath.com` or `telnet cloud.uipath.com 443`.
2. If the connection fails, ask your network team to allow outbound HTTPS traffic to `cloud.uipath.com` from the Jira Server host.
3. Confirm the **Server URL** field in the Jira plugin follows the format `https://cloud.uipath.com/{OrgName}/{TenantName}/testmanager_`.
4. Confirm the API key was copied and pasted correctly from Test Manager, and that it has not expired.

:::note
Basic Authentication is the only supported authentication method for the Jira Server (Jira Data Center) connection and cannot be changed.
:::

## My Jira "Test" issue type synced as a Requirement instead of a Test Case

### Solution

The native Jira integration supports only two issue types: Requirements and Defects. A custom issue type from a test-management add-on, such as Xray's "Test" or Zephyr's equivalent, has no native mapping to a Test Manager Test Case, so it syncs as a Requirement instead. To sync custom issue types as Test Cases, use [Test Manager Connect](https://docs.uipath.com/test-manager/automation-cloud/latest/user-guide/uipath-test-manager-connect#test-manager-connect) instead of the native integration.