- 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
- Importing 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
- Searching with Autopilot
- Project operations and utilities
- Test Manager settings
- ALM tool integration
- API integration
- Troubleshooting
Test Manager user guide
Integrate your Atlassian Jira instance to Test Manager to add defect reports, and assign stories and requirements to your tests. The integration works with all Jira project types.
To integrate Jira to Test Manager, follow these procedures:
Step 2: Configure a a Jira connection
Step 3: Configure Jira project
Supported object types and data transfer direction
Supported objects
- Items synchronized from Jira to Test Manager are read-only except for attachments, object labels and test case links.
- Defects are synchronized from test executions in Test Manager to Jira.
Data transfer
The direction of data transfer and corresponding objects are listed in the following table:
| Xray for Jira | Direction | UiPath Test Manager |
|---|---|---|
| Requirements | → | Requirements |
| Defect | ← | Defects |
Install UiPath® Test Manager for Jira
Install the UiPath® Test Manager for Jira app from the Atlassian Marketplace to enable the integration between your Jira instance and Test Manager.
- Open your Jira instance in your browser.
- Log in as an administrator.
- Select Manage Apps from the administration menu.
- Under Find new Apps search for UiPath®.
- Select UiPath® Test Manager for Jira.
- Select Install.
The latest version of UiPath® Test Manager for Jira is installed.
Configure Jira Connection
All the objects that you create in Test Manager will have the identity of the Jira user used for this connection. The connection is established based on the type of Jira product that you are using. For Jira Data Center, you need to set a connection for Jira Server. For Jira Cloud, you need to configure a connection for Jira Cloud:
- Log in to Test Manager as an administrator.
- Open your project.
- Navigate to Project Settings > Integration.
- 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. For more information on Atlassian API tokens, see Manage API tokens for your Atlassian account.
- Defect Type: Specify the Jira object-type to be used for defects. Usually, that will be 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.
6. Select Save. 7. Select the connection to expand the panel and copy the API Key for later use.
Configure Jira Project
Connect a specific Jira project to Test Manager by configuring the issue types to synchronize as requirements and providing the Test Manager server URL and API key.
-
Open Jira and navigate to the project you want to integrate with Test Manager.
-
Switch to the project settings.
-
Scroll down and select UiPath® Test Manager to open the Test Manager configuration page.
-
Select all Jira issue types that you want to be synchronized as requirements to Test Manager.
-
Enter the Server URL from Test Manager (e.g.,
https://govcloud.uipath.us/{organizationName}/{tenantName}/testmanager_). -
Paste the API Key you copied at step 7 from the previous procedure.
-
Select Save.
Manage Jira connections
Edit a Jira connection
Edit your connection settings.
- Log in to Test Manager as an administrator.
- Open your project.
- Navigate to Project Settings > Integration.
- Select a Jira connection to expand the panel.
- Select Edit to configure the connection.
- Select Save to confirm changes.
Delete a Jira connection
Delete the selected connection and its associated requirements.
- Log in to Test Manager as an administrator.
- Open your project.
- Navigate to Project Settings > Integration.
- Select a Jira connection to expand the panel.
- Select Delete to remove the connection.
- Select Ok to confirm.
Related articles
Result
The Jira project is connected to Test Manager. Requirements are synchronized from Jira to Test Manager, and defects created in Test Manager are synchronized back to Jira.