- Getting started
- Project management
- Documents
- Working with Change Impact Analysis
- Create test cases
- Assigning test cases to requirements
- Cloning test cases
- Exporting test cases
- Linking test cases in Studio to Test Manager
- Delete test cases
- Manual test cases
- Document test cases with Task Capture
- Parameters
- Enabling governance at project level
- Disabling governance at project level
- Enabling governance at test-case level
- Disabling governance at test-case level
- Managing approvers for governed test cases
- Managing governed test cases in the In Work state
- Managing governeed test cases in the In Review state
- Managing governed objects in the Signed state
- Managing comments for governed test cases
- Applying filters and views
- Importing Orchestrator test sets
- Creating test sets
- Adding test cases to a test set
- Assigning default users in test set execution
- Enabling activity coverage
- Enabling Healing Agent
- Configuring test sets for specific execution folders and robots
- Overriding parameters
- Cloning test sets
- Exporting test sets
- Applying filters and views
- Accessibility testing for Test Cloud
- Project operations and utilities
- Test Manager settings
- ALM tool integration
- API integration
- Coding Agents for Testing
- Troubleshooting
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:
- From the Jira Server host, verify outbound connectivity to
cloud.uipath.comon port 443, usingcurl -v --connect-timeout 10 https://cloud.uipath.comortelnet cloud.uipath.com 443. - If the connection fails, ask your network team to allow outbound HTTPS traffic to
cloud.uipath.comfrom the Jira Server host. - Confirm the Server URL field in the Jira plugin follows the format
https://cloud.uipath.com/{OrgName}/{TenantName}/testmanager_. - Confirm the API key was copied and pasted correctly from Test Manager, and that it has not expired.
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.