⚠️ Requirements are available in Startup, Business, and Enterprise subscriptions
Requirements in Qase represent the business rules, features, or user stories your product must satisfy.
Each requirement links to the test cases that verify it, helping you keep track of how functionality is being validated.
Requirements support a parent–child hierarchy, so you can model epics that break down into features and user stories.
Creating a requirement
Go to the Requirements section in your project and select + Requirement.
Each requirement includes the following properties:
Property | Details |
Title | A clear name for the requirement. |
Description | Optional context, acceptance criteria, links to specs, or any detail that helps testers understand intent. |
Parent | Nest this requirement under another to build a hierarchy. Defaults to “Root” if no parent exists. |
Status | Valid, Draft, Review, Rework, Finish, Implemented, Not Testable, or Obsolete. |
Type | Epic, User Story, or Feature. |
Attachments | Supporting files such as mockups or specification documents. |
Linked test cases | The test cases that cover this requirement. |
Working with requirements
Once created, each requirement shows its linked cases, status, and hierarchy in the requirements list. From a requirement's detail view, you can:
Create child requirements to break down a high-level epic into testable pieces.
Edit or delete the requirement.
Navigate to linked test cases by clicking their titles, useful for reviewing coverage.
The requirements list supports search (by title or description) and filtering by author, status, type, or creation date.
Linking test cases to requirements
You can link test cases to requirements directly from the requirement, select the relevant test cases while creating or editing it.
FAQ
Can I create a requirement without linking test cases?
Yes. You can create requirements first and link test cases later as they are written.
What happens if I delete a requirement?
Deleting a requirement does not delete the linked test cases. It only removes the association between them.
Can I move a requirement to a different parent?
Yes. You can update the parent field at any time to reorganize your hierarchy.