Requirements

It is very common to use specialized requirements management tools to manage requirements like user stories, epics, or other artifacts. Test Manager supports the synchronization of requirements from external tools as well as the creation of requirements from within Test Manager. In a Test Manager project, there can be requirements that are synced from external tools as well as requirements that were created in Test Manager.

Navigation and Search

To quickly find your requirements, use the search function and the filters. Navigate within the page using and configuring the paginator. Alternatively, you can use the breadcrumb to navigate between the pages.

You have two filter tabs to choose from:

Browse - to list all requirements.
Updated by me (predefined) to list only the requirements that have been updated by the current user, running the Test Manager instance.
Use the search bar to find requirements by their key, name or labels (requires full search term match). You can use the search bar at the top of the page to look for items across Test Manager (e.g., test sets, test cases).

Creating Requirements

To create requirements in a Test Manager project:

In the Test Design menu, navigate to the Requirements page.
Click Create Requirement. The Create Requirement window is displayed.
Fill in the fields accordingly:
- Name - The name for your requirement.
- Description - (Optional) Add any description to the requirement. In order to add formatted text, use Markdown syntax.
- Optionally, add any number object labels.
Click Create. Your new requirement is displayed in the Requirements page.

Tip: Upload documents

Synchronizing Requirements From External Tools

In order to keep requirements from external ALM tools in sync with requirements from Test Manager, configure a connection first. Refer to About ALM Tool Connectors to learn how to configure a project to be synchronized with an external ALM tool.

Once a connection is configured properly, any requirement which is created in the external tool is also created in Test Manager. The name and description of those requirements are also kept in sync when changed in the external tool. In Test Manager, these attributes are read-only.

Note: After a connection to an external ALM system has been configured, no initial synchronization of existing artifacts is performed. This should avoid creating huge amounts of data in Test Manager without any prediction on how long this would take. However, whenever an object in the external tool is updated, it will be created in Test Manager in case it does not exist.

Jira Requirements

Synchronizing Objects from Jira to Test Manager

Test Manager comes with a Jira connector pre-installed. On your Jira instance, the UiPath® Test Manager for Jira apps needs to be installed from the Atlassian marketplace. See Connecting a Jira Project to learn how to configure Jira and Test Manager to enable synchronization.

Objects are synchronized from Jira to Test Manager under the following circumstances:

An object is created in Jira and Jira is configured to synchronize this type of object.
An object is updated in Jira and Jira is configured to synchronize this type of object.

Note:
If an object is updated in Jira which does not exist in Test Manager, a new requirement will be created in Test Manager.

If an object is deleted in Jira, the synchronized object in the Test Manager will remain. Test Manager never propagates deletions across systems.

Enforcing Synchronization

For a particular object, synchronization can be enforced immediately. This can be helpful under the following circumstances:

Objects are out-of-sync for any reason - for example, Test Manager was not available while the Jira object was updated.
A new Jira connection has been set up in Test Manager and objects which already existed in Jira need to be synced.

To enforce synchronization of an object:

Open the object in Jira.
Click Push to Test Manager from the More menu. Synchronization is invoked immediately.

Note: Please note that Test Manager does not perform a sync-all operation after a Jira connection has been set up.