Requirements Overview
2 min read
Requirements describe what a project needs to build, fix, improve, or validate. In Hawzu, requirements help teams connect planned work to test cases, releases, testruns, executions, defects, labels, and coverage views.
Use requirements when your team needs a clear way to answer: what are we validating, where is it tested, and what is still missing coverage?
What Requirements Track
Section titled “What Requirements Track”A requirement can include:
- A required Title
- A rich Description
- A Type
- A Status
- One or more Labels
- Project custom fields
- Linked test cases
- Related releases, testruns, executions, and defects
Requirements are project-level records. They belong to the current project and are available to other project areas that support requirement traceability.
Opening Requirements
Section titled “Opening Requirements”To open project requirements:
- Open a workspace.
- Open a project.
- Select Requirements from the project navigation.
The Requirements page lists the requirements in the project and gives you tools to search, filter, sort, create, and open requirement details.
Requirements Page
Section titled “Requirements Page”The Requirements table can show:
- Name
- Type
- Status
- Labels
- Created By
- Created On
- Testcases
The Testcases column shows whether the requirement is connected to test cases, releases, or testruns. Requirements with no usage are easy to spot, which helps teams find missing coverage.
You can also choose which columns are visible by using the column control in the page header.
Requirement Types
Section titled “Requirement Types”Hawzu supports these requirement types:
- Feature
- Bug Fix
- Performance
- Enhancement
Types help group requirements by the kind of work they represent.
Requirement Statuses
Section titled “Requirement Statuses”Hawzu supports these requirement statuses:
- Draft
- In Progress
- In Review
- Approved
- Rejected
Statuses help your team understand where each requirement sits in the review and validation process.
Requirement Details
Section titled “Requirement Details”Opening a requirement shows its details view. From there, you can review or update the requirement depending on your project access.
The details view includes:
- Requirement title and description
- Type and status
- Labels
- Custom fields
- Linked test cases
- Releases and testruns that use the requirement
- Defects linked directly to the requirement
- Defects linked through the requirement’s test cases
Permissions
Section titled “Permissions”Requirement visibility and actions depend on project access. Users need the right project permissions to view, create, update, or delete requirements.
Users without create or update access can still view requirements when their project role allows it.
Next Steps
Section titled “Next Steps”- Learn how to create requirements
- Review how to manage requirements
- Understand where requirements are used