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?
A requirement can include:
Requirements are project-level records. They belong to the current project and are available to other project areas that support requirement traceability.
To open project requirements:
The Requirements page lists the requirements in the project and gives you tools to search, filter, sort, create, and open requirement details.
The Requirements table can show:
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.
Hawzu supports these requirement types:
Types help group requirements by the kind of work they represent.
Hawzu supports these requirement statuses:
Statuses help your team understand where each requirement sits in the review and validation process.
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 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.