Built-in Requirements
Create and manage requirements directly in TestKase.
Overview
TestKase provides full built-in requirement management for teams that do not need an external integration. You can create requirements directly in TestKase, organize them into folders, set priority and status, link them to test cases and defects, and attach supporting files -- all without connecting to any external platform.
Key Capabilities
- Create requirements -- Add requirements manually with a title, description, and rich text content.
- Organize in folders -- Group requirements into a folder hierarchy for structured navigation.
- Set priority and status -- Assign priority levels (P0 through P3) and track status (Open, In Progress, Closed, Archive).
- Link to test cases and defects -- Establish traceability by linking requirements to the test cases that verify them and the defects discovered against them.
- Attach files -- Upload supporting documents, screenshots, or specifications directly to a requirement.
Built-in requirements belong to the project's Built-in requirement integration. If you later switch that project's requirement integration to anything else -- the Jira, GitHub or GitLab card under API Integrations, the Jira Plugin, or a Chrome Extension card -- or reset the Built-in integration, TestKase permanently deletes every requirement and every requirement folder in the project. Connecting the Jira Plugin or a Chrome Extension card on the Defect Integration page does the same thing, because one configuration covers both types.
Requirements are not migrated and cannot be recovered. The deletion happens when you confirm the Data Loss dialog, before the new connection is saved, so cancelling the rest of the wizard does not undo it. Export anything you need first.
For the complete guide including folder organization, field details, and attachments, see Built-in Requirements.