Requirement Details

4 min read

Opening a requirement shows its detail view. From here you can review the requirement’s title, description, type, status, owner, parent, 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, who owns it, and what is linked to it?

Opening a Requirement

To open a requirement’s details:

Open a workspace.
Open a project.
Select Requirements.
Select a requirement to open its detail view.

Depending on your project access, you can review the requirement or switch into editing to update it.

Requirement Information

The main panel shows the requirement’s core information:

Title
Description
Type
Status
Owner
Parent requirement
Labels
Custom Fields, when the project defines them

The header also shows the requirement code, who created it, and when it was created, along with a Subscribe control.

Owner

The Owner is the project user responsible for the requirement, shown as a badge (or Unassigned). While editing, pick an owner from the project’s users, or use Assign me to take ownership yourself. Assigning a user owner also subscribes them to the requirement.

Parent Requirement

The Parent requirement shows where this requirement sits in the hierarchy. A top-level requirement shows Top-level requirement. While editing, you can change the parent to move the requirement under a different one, or clear it to promote the requirement to the top level. See Sub-requirements & Hierarchy.

Use the Subscribe button in the header to watch the requirement. Once subscribed, the button reads Subscribed and you receive updates when the requirement changes.

The creator and any assigned user owner are subscribed automatically.
Updates appear under the Requirement updates category in Notifications.
You can subscribe or unsubscribe at any time — it is a personal setting and does not affect other users.

You can also toggle subscriptions directly from the Subscribe column on the Requirements page.

The requirement detail view includes tabs for the work connected to the requirement:

Testcases
Releases & Testruns
Defects
Sub-items
Comments
Change History

On smaller screens, these tabs open in a separate panel using the Related button.

Testcases Tab

The Testcases tab shows the test cases linked to the requirement, split into two groups:

Directly linked — test cases tagged to this requirement. When editing, use Add / Update Testcase to change them.
From sub-requirements & tasks — test cases that come from the requirement’s sub-requirements and tasks. These are shown for context and are read-only here; manage them on the sub-requirement or task that owns them.

If no test cases are linked, the tab shows an empty state.

Releases & Testruns Tab

The Releases & Testruns tab shows where the requirement is used in test activity. It is organized into:

Releases — releases tagged to the requirement, along with any related executions.
Testruns — testruns tagged to the requirement.

When the requirement has sub-requirements or tasks, this tab separates Directly Linked activity from activity Linked via Sub-requirements & Tasks. Each item links out to the related release, execution, or testrun. When nothing is tagged, the section shows an empty state.

Defects Tab

The Defects tab shows defects connected to the requirement, grouped into:

Directly Linked Defects — defects linked to the requirement itself.
Defects Linked via Testcases — defects linked through the requirement’s test cases.
Defects Linked via Sub-requirements & Tasks — shown when the requirement has sub-requirements or tasks.

Each defect links out to its detail view and shows its current status.

Sub-items Tab

The Sub-items tab holds the items nested under the requirement:

Sub-requirements — child requirements, each shown as a card you can click to open. See Sub-requirements & Hierarchy.
Tasks — lightweight owned items under the requirement, each showing its code, title, owner, and status. Click a task to open its detail view.

While the requirement is in edit mode, you can add a task here: type a title, optionally set an owner, and click Add task. New tasks start with the To do status. See Tasks for the full task workflow.

Comments Tab

The Comments tab shows discussion on the requirement. Use it to add context, ask questions, or capture decisions alongside the requirement. You can @-mention project users.

Change History Tab

The Change History tab shows a timeline of edits made to the requirement, so you can see what changed, who changed it, and when.

Tracked changes include:

Creation of the requirement
Title, description, type, and status changes
Owner and parent requirement changes
Label and custom field updates
Test cases being linked and unlinked
Comments added, edited, or removed

You can filter the timeline by field type and sort it Newest or Oldest first. Description and comment edits offer a View diff option so you can compare the before and after.

Editing a Requirement

Click Edit Requirement to switch the main panel into edit mode. You can update the title, description, type, status, owner, parent requirement, labels, custom fields, and directly linked test cases. Click Save Changes to save, or Cancel to discard your changes.

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

Deleting a Requirement

Click Delete to remove the requirement. A confirmation dialog explains what will be removed. Deleting a requirement also removes its sub-requirements and tasks. See Delete Requirements for details.

Permissions

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. Anyone who can view a requirement can subscribe to it.

Review Requirements Overview
Explore Sub-requirements & Hierarchy and Tasks
Learn how to Manage Requirements
Understand where requirements are used