Manage Requirements

3 min read

Use the project Requirements page to review, organize, and update requirements as work changes.

The Requirements Tree

The Requirements page shows requirements as an expandable tree. Sub-requirements and tasks are nested under their parent:

Click the chevron on a row to expand or collapse its children.
Sub-requirements are listed before tasks under the same parent.
Requirement rows use a folder icon; task rows use a checklist icon and show their TASK- code inline.

The tree starts fully expanded. There are no page controls — the full list scrolls within the page, and searching or filtering narrows what you see.

Search And Filter

The Requirements page supports search and filters so you can narrow the list.

Search matches a row’s code, title, type, status, owner, labels, and creator.

You can filter by:

Type
Status
Owner
Created By
Creation Date
Labels (including a Without Labels option)
Requirement custom fields with dropdown-style values

When a filter matches a nested item, its parent requirements stay visible so you keep the surrounding context. Use Clear All to remove active filters and return to the full tree.

Sort Requirements

You can sort requirements by:

Code
Title
Type
Status
Owner
Created By
Created On

The Code, Title, and Created On column headers are also clickable to sort directly. The default sort is Created On, newest first. Whatever sort you choose, sub-requirements always sort before tasks under the same parent.

Choose Visible Columns

Use the column control in the Requirements page header to choose which columns appear in the table. Available columns are:

Code
Title
Type
Status
Owner
Labels
Created By
Created On
Testcases
Defects
Tasks
Subscribe

The Code and Title columns are always visible and stay pinned as you scroll horizontally. Other columns can be shown or hidden based on how your team reviews requirements, and your choice is remembered.

Review Usage

Several columns roll up coverage across a requirement’s whole subtree (the requirement, its sub-requirements, and their tasks):

Testcases — the combined, de-duplicated number of linked test cases. A requirement with none shows a dash, which helps teams find requirements that may still need coverage.
Defects — a breakdown of linked defects by status.
Tasks — a done/total roll-up of the requirement’s tasks, shown green when all tasks are done.

The Subscribe column lets you watch a requirement or task directly from the table. Click Subscribe to start receiving updates; the button then reads Subscribed. See Requirement Details for how subscriptions work.

Open Requirement Details

Select a requirement row to open its details view, or a task row to open the task view.

The details view shows the title, description, type, status, owner, parent, labels, custom fields, linked test cases, sub-requirements and tasks, related releases and testruns, and linked defects. See Requirement Details.

Edit A Requirement

To edit a requirement:

Open the requirement.
Click Edit Requirement.
Update the fields you need.
Click Save Changes.

You can update:

Title
Description
Type
Status
Owner
Parent requirement
Labels
Active custom fields
Directly linked test cases

The Releases & Testruns and Defects tabs are review-only while editing.

Organize the Hierarchy

You can restructure requirements by changing a requirement’s Parent requirement while editing it — move it under another requirement, or clear the parent to promote it to the top level. You can also add tasks from a requirement’s Sub-items tab while editing. See Sub-requirements & Hierarchy and Tasks.

Permissions

Managing requirements depends on your project access. Users need update access to edit requirements, change fields, update linked test cases, add tasks, or change labels. Anyone who can view a requirement can subscribe to it.