Skip to main content

Deleting requirements in the requirements library

How to delete requirements in the requirements library

Updated over 2 months ago

Initial access requirement: User rights

The authorization to delete requires the user right “Manage playbooks”.

Only users who have been assigned this administrative right can initiate the deletion process for a test requirement. This ensures that only authorized personnel can make profound changes to the available test criteria.

The deletion process is secured in two stages:

  1. Deletion lock for active links:
    If a test requirement is used in one or more playbooks, it cannot be deleted immediately. The system displays a list of the affected playbooks. The user must manually remove the requirement from all playbooks (“detach”) before the actual deletion in the library can be completed.

  2. Cascading deletion when removing playbooks:

  • Exclusive requirements that are only contained in the playbook to be deleted are automatically deleted as well.

  • Shared requirements that are referenced in other active playbooks are retained.

Did this answer your question?