Skip to content
Hawzu Docs

Delete Requirements

2 min read

Delete a requirement only when it should no longer be part of the project. Deletion is permanent and cannot be undone.

Delete A Requirement

Section titled “Delete A Requirement”

To delete a requirement:

  1. Open the project Requirements page.

  2. Select the requirement.

  3. Click Delete in the requirement details view.

  4. Review the confirmation message.

  5. Click Delete Requirement.

The delete action is available only to users with permission to delete requirements.

What Gets Removed

Section titled “What Gets Removed”

Deleting a requirement removes:

  • The requirement record
  • Requirement details
  • Requirement attachments
  • Links between the requirement and test cases
  • Links between the requirement and defects
  • All of the requirement’s sub-requirements and tasks

The requirement is removed from the active project Requirements list.

Deleting a requirement deletes everything nested under it. All of its sub-requirements and their tasks are deleted along with it. Review the tree before deleting a parent requirement.

What Is Not Deleted

Section titled “What Is Not Deleted”

Deleting a requirement does not delete:

  • Test cases
  • Releases
  • Testruns
  • Past executions
  • Defects
  • Project labels

Existing releases and past executions are not affected by requirement deletion.

Deleting a Task

Section titled “Deleting a Task”

Tasks are deleted individually from the task’s own view using its Delete button. Deleting a task removes it from its requirement and unlinks it from any test cases, but does not delete the test cases, releases, executions, or defects it was linked to. Deleting a requirement deletes its tasks automatically. See Tasks.

Traceability Impact

Section titled “Traceability Impact”

After deletion, the requirement is no longer available for new traceability links, test-case selection, test-run selection, or requirement filters.

Any requirement links that depended on the deleted requirement are removed from active project traceability.

Before Deleting

Section titled “Before Deleting”

Before deleting a requirement, review:

  • Its sub-requirements and tasks — these will be deleted too
  • Linked test cases
  • Releases and testruns shown in the requirement details view
  • Directly linked defects
  • Defects linked through the requirement’s test cases

If the requirement still represents active work, consider updating its status (for example, to Archived) instead of deleting it.

Next Steps

Section titled “Next Steps”