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 and IP restriction errors.

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 instead of the native integration.

Jira Cloud sync fails with "Unauthorized for syncing this requirement"

Solution

If syncing from Jira Cloud to Test Manager fails with Requirement sync-status: Unauthorized for syncing this requirement. Please recheck your api-key., the API key is not always the cause. The error can also occur when IP restriction is enabled for your UiPath organization.

The UiPath® Test Manager for Jira app sends requests from Atlassian Forge IP addresses. If these addresses are not allowed, the UiPath platform rejects requests from Jira to Test Manager with a 403 status code before they reach Test Manager. Synchronization from Test Manager to Jira can still work.

To resolve the issue:

1. Check that the API key in the Jira app is correct and belongs to the right Test Manager connection.
2. Compare the version of the UiPath® Test Manager for Jira app installed on your Jira instance with the version listed on the Atlassian Marketplace.
3. If the versions differ, install the version listed on the Atlassian Marketplace and uninstall any other version.
4. Ask a UiPath organization administrator to go to Admin > Security > IP restriction, and add the egress IP ranges that Atlassian publishes at ip-ranges.atlassian.com, or exempt your organization from IP restriction.

Note:

Atlassian does not use static IP addresses and can change its IP ranges at any time. Keep the allowed list in sync with the ranges published by Atlassian. If the allowed list is out of date, synchronization can fail intermittently.