Requirements

The Requirements tab tracks the tasks you're building and how well your test cases cover them, so you always know what still needs testing before a release.

Tasks and requirements

Requirements are organized around tasks — work items you enter manually (for example, mirrored from your task tracker). Each task can have a name, an external ID, a link back to the original task, and a description; only the name is required.

Inside a task you add one or more requirements — individual statements of what needs to work. The task list is a simple accordion: click a task to expand its requirements in place.

Each requirement has a status that reflects where it stands:

You can change a requirement's status manually at any time using the status dropdown next to it.

Use search to filter tasks by name or external ID. Tasks you no longer need can be archived (hidden from the default view, but still available if you show archived tasks) or deleted (which also removes their requirements).

Linking test cases to requirements

You can link test cases to a requirement from either side:

• From the requirement — click the case counter/link button on a requirement to open a picker. The picker mirrors the case tree from the Cases page: a panel of folders on the left ("Linked", "All cases", "No folder", and your folder tree) and the matching cases on the right, with search by name, case number, or full reference (for example KEY-12). Check the cases you want linked and save — this replaces the full set of linked cases for that requirement.
• From the test case — open the case and use the Requirements section to see everything it's linked to, search for more requirements (grouped by task), and remove links. Changes are saved together with the rest of the case.

Linking is many-to-many: a requirement can have several cases, and a case can cover several requirements.

Automatic status changes

Linking your first test case to a ready requirement automatically moves it to covered. Removing the last linked case from a covered requirement moves it back to ready. Statuses draft and not_required are never changed automatically — you're always free to mark a requirement covered by hand, even without linked cases, if it's verified outside the system.

If a requirement's status and its linked cases disagree (for example, covered with zero cases, or cases linked to a requirement that isn't covered), a warning icon appears next to it with an explanation on hover. This is informational only — nothing is blocked.

Coverage

Each task shows a badge like "covered 3 of 5", counting requirements that are covered against all requirements except not_required ones. A task where every requirement is covered gets a green badge.

The Requirements page also shows a project-wide coverage summary above the list ("covered M of N · X%"), and the statistics dashboard has a coverage tile showing the same percentage. Both ignore search filters and archived-task visibility, and both are calculated the same way, so the numbers always agree.

Task versions

You can tag a task with a version (for example "59" or "59.1") to match your team's release or sprint naming. Tasks are grouped by version in the list, newest version first, with untagged tasks grouped last under "No version". A version filter in the toolbar lets you narrow the list to a specific version or to tasks with no version at all.