Skip to main content
Knowledge Base

Create & Manage Requirements - Build Traceability from Scope to Testing

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
TestCaseLab Requirements page showing ten payment requirements grouped in the Payments category.

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’.

Requirements category menu showing options to rename, create a subcategory, or delete the Payments 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.

Requirement details panel for Payment Module Epic showing its category, type, status, description, tags, and attachments.

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.

Requirement Test Cases tab showing no linked test cases and a Link Test Cases action.

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.

Link Test Cases dialog showing a suite list and selected test cases ready to link to a 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.

Requirement Defects tab showing two failed test runs linked to reported issues.

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!

Browse Knowledge Base

Use AI Assistant to Create Test Cases and Requirements

The AI Assistant helps you create and review QA artifacts inside your project using natural language.

Olha Holota
Test CasesRequirements

Create & Manage Suites - Group and Structure Your Test Cases

Suites are essential for organizing your test case repository into logical categories. With up to 4 levels of subsuites, you can structure your test cases to align with your project’s needs.

Olha Holota
Test CasesSuites

Create & Manage a Test Case - Start Testing Quickly

Creating test cases ensures your testing process is structured and thorough. TestCaseLab offers two methods to add test cases—quick and detailed. Follow this guide to get started.

Olha Holota
Test Cases

Organize Your Testing Process

Start using TestCaseLab now as your test case management system and bring your Quality Assurance at the top-level!

Get Started for Free

No Credit Card Required