Make the most out of your experience and check
articles about TestCaseLab functionality

The Requirements page helps your team define, organize, and track product requirements inside a project.

Requirements can be linked to Test Cases, giving your team clear traceability from product scope to test coverage, execution, and defects.

1. Open the Requirements Page

To work with requirements:

• Open your project.
• Go to the Requirements page.
• Use the page to create requirements, organize them by category, and link them to Test Cases.

The Requirements page includes:

• Categories tree
• Requirements list
• Requirement details panel
• Search
• Sorting
• Filters
• Bulk Actions

2. Create Requirement Categories

Categories help organize requirements into logical groups.

To create a category:

• Go to the Categories section.
• Click the ‘+’ button.
• Enter the category title.
• Save the category.

You can create nested categories up to 4 levels deep.

You can also:

• Rename categories.
• Create subcategories.
• Rearrange categories with drag and drop.
• Delete categories.

Note: Deleting a category does not delete the requirements inside it. Requirements are moved to the parent category or to ‘Requirements without Category’.

3. Create a Requirement

To create a requirement:

• Select a category.
• Click ‘+ Requirement.’
• Enter the requirement title.
• Click on the requirement to see Requirement Details.
• In the Requirement Details set:
  
  • Requirement type
  • Requirement status
  • Add a description, tags, assignees, or attachments if needed.

Available requirement types include:

• Epic
• Feature
• User Story
• Use Case
• Functional Requirement
• Non-Functional Requirement
• Business Requirement

Note: ‘User Story’ is the default requirement type.

4. Manage Requirement Details

Click a requirement row to open the Requirement Details panel.

From the details panel, you can view and update:

• Title
• Category
• Type
• Description
• Status
• Tags
• Assignees
• Attachments
• Metadata

The details panel also includes tabs for:

• Details
• Test Cases
• Defects
• Audit Log

Note: Requirement descriptions support plain text and markdown.

5. Link Requirements to Test Cases

Use the Test Cases tab to link requirements with related Test Cases.

To link Test Cases:

• Open a requirement.
• Go to the Test Cases tab.
• Search for Test Cases by title or key.
• Select the Test Cases you want to link.

Linked Test Cases are synchronized both ways. If you link a Test Case from the requirement, the requirement also appears in the Test Case’s Related Requirements field.

Note: Up to 10 Test Cases can be linked to one requirement.

6. Track Defects from Linked Test Cases

The Defects tab shows defects connected to test results from linked Test Cases.

You can view:

• Last tested date
• Defect count
• Test Run
• Test Result status
• External defect link
• Timestamp

Use this tab to understand whether a requirement has known issues based on related test execution.

7. Use Requirement Filters and Search

Use filters to narrow down the Requirements list.

Available filters include:

• Assignee
• Category
• Status
• Type
• Tags
• Orphaned requirements

You can also search by:

• Requirement title
• Requirement key
• Requirement details

Note: An orphaned requirement is a requirement that has no linked Test Cases.

8. Use Bulk Actions

Bulk Actions help update multiple requirements at once.

Available Bulk Actions include:

• Edit
• Duplicate
• Delete
• Assign
• Status update

Bulk Actions follow the same behavior and confirmation patterns as Test Cases.

9. Import and Export Requirements

You can import requirements from CSV, including:

• Categories
• Requirement Title
• Requirement Description
• Status
• Type
• Tags

You can also export requirements to CSV.

10. View Requirement History

The Audit Log tab shows changes made to the requirement.

Tracked changes include:

• Field updates
• Status changes
• Tag changes
• Attachment changes
• Test Case linking and unlinking
• Requirement deletion and restoration

What’s Next?

Use Requirements to connect product scope with test coverage and execution results. For additional help, check related guides or contact support—we’re here to help!

‍

Project Milestones help you organize Test Runs around release goals, testing windows, or QA deadlines. Use milestones to group related Test Runs, track progress, and quickly identify missed deadlines.

Milestones are optional. You can continue using Test Runs without milestones if your workflow does not require deadline tracking.

1. Create a Project Milestone

To create a milestone, you have to be a Project Administrator. Please follow the instructions:

• Open your project.
• Go to the Milestones page.
• Click the ‘+ Milestone’ button.
• Fill out the milestone details:
  • Title: Enter a clear milestone name.
  • Description: Add optional context, links, or release notes.
  • Start Date: Set the beginning of the testing window, if needed.
  • Due Date: Set the deadline for the milestone, if needed.
  • Test Runs: Select the Test Runs that should belong to the milestone. You'll be able to add Test Runs later.
• Save the milestone.

Note: Project Milestones are created at the project level and do not apply across multiple projects.

2. Assign Test Runs to a Milestone

You can assign Test Runs to a milestone from:

• The Milestone details page.
• Test Run settings or Test Run details.

A milestone can include multiple Test Runs. Each Test Run can be assigned to one milestone at a time.

3. Understand Due Date Logic

If a milestone has a Due Date, assigned Test Runs inherit that due date.

When a Test Run inherits a due date from a milestone:

• The due date is shown on the Test Run.
• The due date is read-only on the Test Run.
• The milestone is shown as the source of the due date.

If a Test Run is not assigned to a milestone, you can set a manual due date directly on the Test Run.

Note: If no milestone is assigned and no manual due date is set, the Test Run has no due date by default.

4. Track Missed Deadlines

A Test Run is considered missed when:

• The due date has passed.
• The Test Run is not Completed.

Missed deadlines are highlighted in the Test Runs list and on the Test Run details page.

If the due date comes from a milestone, the Test Run will show the milestone as the source.

5. View Milestone Progress

The Milestones list helps you monitor testing progress across time-bound goals.

The list includes:

• Title
• Start Date
• Due Date
• Test Run status summary
• Completion progress
• Test Runs count

Use filters to focus on milestones by status, date range, or missed Test Runs.

6. Open Milestone Details

The Milestone details page gives a full overview of milestone progress.

You can view:

• Milestone title and status.
• Start and due dates.
• Total Test Runs list.

From the Test Runs section, you can open a Test Run, edit it, or remove it from the milestone.

7. Manage Milestones

Project Administrators can:

• Edit milestone details.
• Archive milestones.
• Restore archived milestones.
• Delete milestones.
• Assign or remove Test Runs.

Other project roles have read-only access to milestones.

What’s Next?

Use Project Milestones to organize testing around releases, deadlines, or regression cycles. For additional help, check related guides or contact support—we’re here to help!

‍

Customizing your test case template ensures your project workflow matches your team's unique needs. Follow these steps to configure test case types, tags, and custom fields.

Learn what is a Test Case here.

‍

1. Access Project Settings

• Go to the project where you want to customize the test case template.
• Navigate to Project Settings to begin customization.

Note: Only Project Administrators can access Project Settings.

‍

2. Manage Test Case Types

Types allow you to filter and organize test cases, making it easier to locate specific cases.

• Open the Test Case Types page in Project Settings.
• Use the predefined list of types or add your own based on your project needs (e.g., Approved, Pending Approval, Draft).
• Set a default type for new test cases. 

Note: The Type assigned by default to a Test Case can be updated individually in the Test Case Details.

‍

3. Manage Test Case Tags

Tags help filter the test case list, enabling quick and easy navigation.

• Go to Project Settings > Test Case Tags to manage your tags:
  • Rename tags to keep them relevant.
  • Delete tags that are no longer needed.

Note 1: Creating tags is available while editing a test case by typing into the ‘Tags’ field.

Note 2: Use the test case list filter to filter by tag, or simply click on a tag to apply the filter directly.

‍

4. Add Custom Fields

Expand your Test Case Template by adding extra fields (text areas and dropdowns).

• Navigate to Custom Fields in Project Settings.
• Create up to 5 custom fields for your project:
  • Text Fields: Add free-text information.
  • Dropdown Fields: Define options for categorization.
• Control visibility of fields on project pages:
  • Show or hide fields on the Test Cases and Test Plan pages.
  • Show or hide fields on the Test Run page.

Examples: Specify details such as devices, versions, browsers, and environments using custom fields.

Note 1: You can filter test cases by dropdown values while working with the test cases list.

Note 2: Custom fields are always visible on the Edit Test Case page for universal editing.

‍

What’s Next?

Customizing your test case template simplifies test management and enhances team collaboration. If you need additional guidance, check out our related articles or contact support. We’re happy to assist!

‍

With TestCaseLab It is possible to run tests and report bugs instantly to your favorite bug-tracking tool. If you're looking for a test case management tool that integrates with GitHub, try TestCaseLab. 

The instructions below will help you set up the integration with the GitHub tool.

‍

1. Generate API token

• First of all, you should log in to your GitHub account.‍

Note: Make sure that you have an active project on your GitHub account to integrate it with your TestCaseLab project. 

• Navigate to your GitHub account and click on your ‘Profile’ icon. Choose the  ‘Settings’ option from the menu.

• On the ‘Profile Settings’ page find ‘Developer Settings’, and click on it.

• Click on the ‘Personal access tokens’ tab and choose the ‘Tokens (classic)’ option. 

• Click on 'Generate new token' and choose the ‘Generate new token (classic)’ option.

• Fill in the ‘Note’ field, and mark up all required checkboxes. Click on the 'Generate token' button.

• Copy your Access token to the clipboard. 

‍

2. Set up Connection

• After that, you need to navigate to your TestCaseLab Company Account, click on ‘Project Settings’ in the sidebar and go to the ‘Integrations’ tab.
• Choose GitHub from the list of Bug tracking tools. 

• Paste your Personal access token, and click on the 'Test connection' button.
• Choose your Project from the list, and confirm the action.
• As long as there are no issues and the Connection is established, you can proceed with Integration and save the changes.

A 'Connected' notification means your connection has been established without any issues, and you are able to report your defects directly to GitHub. 

‍

What’s Next?

If you have any questions, our support team is here to assist you!

‍

The TestCaseLab tool lets you run tests and report bugs right away to your favorite bug-tracking system. TestCaseLab integrates with the Mantis bug-tracking tool, so you can manage defects easily.  

The following instructions will guide you through setting up the Mantis integration.

‍

1. Generate API token

• As a first step you should log in to your Mantis account. 
• Navigate to your Mantis account and click on your ‘Profile’ icon. Choose the  ‘My account’ option from the menu.

• From the ‘My account’ tab go to the ‘API tokens’ tab.

• Fill in the ‘Token name’ field, and click on the 'Create API token' button. Copy your API token to the clipboard. 

‍

2. Set up Connection

• After that, you need to navigate to your TestCaseLab Company Account, click on the ‘Project Settings’ in the sidebar and go to the ‘Integrations’ tab.‍
• ‍Choose the Mantis tool from the list of Bug tracking tools. 

• Paste your API Key to the ‘API Key’ field. 
• Copy your Mantis URL, and paste it to the ‘URL’ field. Example: https://YOURNAME.mantishub.io/
• Click on the 'Test connection' button, then choose your Project from the dropdown menu and confirm the action.

You can report your defects directly to Mantis from TestCaseLab once you receive the 'Connected' notification.

‍

What’s Next?

If you have any questions, our support team is here to assist you!

‍

In software development, TestCaseLab simplifies and optimizes QA processes. Your favorite bug-tracking tool can be used to execute tests and report bugs immediately. You are welcome to try TestCaseLab if you are looking for a test management tool that integrates with Asana. 

To learn how to set Asana test case management tool, follow the instructions below.

‍

1. Generate API token

• First of all, you should log in to your Asana testing tool account to integrate TestCaseLab with Asana. 
• Click on your ‘Profile’ icon and choose the ‘My Settings’ option.

• On the ‘Settings’ page navigate to the ‘Apps’ tab and click on the ‘Manage Developers Apps’ option.

• Click on the 'Create new token' button.

• Fill in the ‘Name’ field, click on the ‘I agree to the API terms and conditions’ checkbox. After that, please confirm the action by clicking on the 'Create token' button.

• Copy your token by clicking on the 'Copy' button and close the modal window by clicking on the 'Done' button. 

‍

2. Set up Connection

• After that, you need to navigate to your TestCaseLab Company Account, click on the ‘Project Settings’ in the sidebar and go to the ‘Integrations’ tab. 
• Choose the Asana test case management tool from the list of Bug tracking tools. 

• Paste your Personal access token, and click on the 'Test connection' button.
• Choose your Workspace and Project from the list, and confirm the action.

The 'Connected' notification indicates that your connection has been established without any issues. From TestCaseLab, you can report your defects directly to Asana. 

‍

What’s Next?

If you have any questions, our support team is here to assist you!

‍

By using the TestCaseLab tool, you can easily run tests and report bugs. The Youtrack bug-tracking tool is easily integrated with TestCaseLab.

Here is a quick guide to configure the integration.

‍

1. Generate API token

• As a first step, you should be logged in to your Youtrack test management account.
• Click on your Profile icon in the header and then go to the ‘Profile’ page by clicking on the respective point from the menu.

• Navigate to the ‘Account Security’ tab.

• Click on the 'New token' button. 

• In the token transition screen enter a Token name, choose a scope (you can choose from suggested by Youtrack), and click on the 'Create' button. 

• Click on the 'Copy token' button.

‍

2. Set up Connection

• After that, you need to navigate to your TestCaseLab Company Account, click on the Project Settings via sidebar and go to the ‘Integrations’ tab.
• Choose Youtrack from the list of Bug tracking tools. 

• Paste your Personal access token to the ‘Personal access token’ field.
• Navigate to your Youtrack account and copy your URL. Example: https://YOURNAME.youtrack.cloud
• ‍After that paste your Youtrack URL to the ‘URL’ field, and click on the 'Test connection' button.
• Choose your Youtrack project from the projects list and confirm the action. 

If you see a 'Connected' notification it means that your connection has been established without any issues and defects can be reported directly from TestCaseLab  to Youtrack.

‍

What’s Next?

If you have any questions, our support team is here to assist you!

‍

It is easy to run tests and report bugs using the TestCaseLab test management system. 

Set up integration with the Pivotal tracker using a short manual below.

‍

1. Generate API  token

• To get started, log into your Pivotal account.
• Сlick on your name in the header and choose the ‘Profile’’ option from the menu.

• Scroll down the Profile page to the ‘Api token’ tab.

• Click on the 'Create new token' button, and copy the created token to your clipboard.

‍

2. Set up Connection

• After that, you need to navigate to your TestCaseLab Company Account, click on the ‘Project Settings' and go to the ‘Integrations’ tab.
• Choose the Pivotal tool from the list of Bug tracking tools. 
• Paste your API token to the ‘API key’ field, and click on the 'Test connection' button.
• Chose a project from the projects list and confirm the action.

Upon receiving a ‘Connected’ notification, your connection has been established without any issues. It means that defects can be reported directly to Pivotal.

‍

What’s Next?

If you have any questions, our support team is here to assist you!

‍

Learn how to set Jira (server-based) integration following the instructions below.

‍

1. Log in to your Jira account

First of all, you should log in to your Jira (Server Based) account to integrate TestCaseLab with Jira. 

‍

2. Set up Connection

• Go to your TestCaseLab Company Account, and open your Project. 
• Click on the Project Settings and navigate to the ‘Integrations’ tab
• Choose the Jira issue-tracking tool from the list
  

• In the respective field enter your Jira URL (required format: http://jira.YOURDOMAIN.com/).
• Enter your Jira Username. 

Note: In order to find your Jira Username please navigate to your Jira Account and click on your Profile‍

• Copy your Username from the Summary tab:
  

• Enter your Jira Password into the integration form. 
• Confirm the action.

You can check your connection by clicking on the 'Test Connection' button.
If there are no issues and the Connection is established, you can proceed with Integration and save the changes.

‍
Once you receive a ‘Connected’ notification, it means your connection is established with no issues and you can report your defects to Jira directly from TestCaseLab.

‍

What’s Next?

If you have questions or need assistance, our support team is always ready to help.

‍

TestCaseLab is a simple and comfortable test management platform for running tests and reporting bugs.

Easily integrate your favorite test case management tool with Redmine! The following list of actions is a short guide to help you get started.

‍

1. Generate API Key

• In order to start the integration you should be logged in to the Redmine test case management tool as Admin.
• From the main page click on the 'Administration' button in the header.

• Click on the ‘Settings’ link in the menu.

• Navigate to the ‘Api’ tab and mark the ‘Enable REST web service’ checkbox. Save changes by clicking on the 'Save' button. 

• Navigate to the ‘My account’ page by clicking on the 'My account' button in the header. 

• Click on the 'Show' button in the side section, and copy your Personal access token to the clipboard. 

‍

2. Set up Connection

• After that, you need to navigate to your TestCaseLab Company Account, click on the Project Settings in the sidebar and go to the ‘Integrations’ tab.
• Choose the Redmine tool from the list of Bug tracking tools. 
• Paste your Personal Access Token to the ‘Personal Access Token’ field.
• Go to your Redmine account and copy your URL. Example: https://YOURNAME.redmineup.com/
• Paste your Redmine URL to the ‘URL’ field in TestCaseLab and click on the 'Test connection' button.
• Choose your Redmine project from the project list and confirm the action.

You will receive a 'Connected' notification once your connection has been established. Redmine can receive defects directly.

‍

What’s Next?

For further assistance, check our related guides or contact support—we’re here to help!

‍