Opening a requirement shows its detail view. From here you can review the requirement’s title, description, type, status, labels, and custom fields, and explore the work connected to it through a set of related tabs.
The detail view helps your team answer: what does this requirement cover, where is it tested, and what is linked to it?
To open a requirement’s details:
Depending on your project access, you can review the requirement or switch into editing to update it.
The main panel shows the requirement’s core information:
The header also shows the requirement code, who created it, and when it was created.
The requirement detail view includes tabs for the work connected to the requirement:
On smaller screens, these tabs open in a separate panel using the Related button.
The Testcases tab shows the test cases linked to the requirement. When editing, you can add or update the linked test cases using the Add / Update Testcase option. If no test cases are linked, the tab shows an empty state.
The Releases & Testruns tab shows where the requirement is used in test activity. It is organized into:
Each item links out to the related release, execution, or testrun. When nothing is tagged, the section shows an empty state.
The Defects tab shows defects connected to the requirement, grouped into:
Each defect links out to its detail view and shows its current status.
The Comments tab shows discussion on the requirement. Use it to add context, ask questions, or capture decisions alongside the requirement.
Available actions in the detail view depend on your project permissions. Users without edit or delete access can still review requirement details when their project role allows it.