Tasks

3 min read

A task is a lightweight item that lives under a requirement. Tasks let multiple teams each own a slice of the same requirement, so you can split delivery work and track it without turning every slice into a full requirement.

Use tasks when one requirement needs to be worked on or validated by several owners in parallel — for example, “API work for Team A”, “Frontend work for Team B”, and “Load testing”.

Tasks vs. Requirements

A task always belongs to exactly one requirement and is intentionally simpler than a requirement:

	Requirement	Task
Belongs to	A project (optionally a parent requirement)	Always one parent requirement
Status	Draft, In Progress, In Review, Approved, Rejected, Archived	To do, In progress, Done
Type	Feature, Bug Fix, Performance, Enhancement	— (shown simply as Task)
Owner	Optional	Optional
Labels	Yes	Yes
Linked test cases	Yes	Yes
Defects & Comments	Yes	Yes
Custom fields	Yes	No
Change history	Yes	No
Sub-items	Sub-requirements and tasks	None (tasks cannot have their own tasks or sub-requirements)

A task gets its own code in the form TASK-n and appears as a leaf item nested under its requirement in the Requirements tree.

Task Statuses

Tasks use a fixed, lightweight set of statuses:

To do
In progress
Done

New tasks start as To do. On a parent requirement, the Tasks column shows a done/total roll-up so you can see how many of its tasks are complete at a glance.

Create a Task

Tasks are created from a requirement’s Sub-items tab, while that requirement is being edited.

Open the parent requirement.
Click Edit Requirement.
Open the Sub-items tab.
In the Tasks section, type a task title (for example, API work for Team A).
Optionally set an Owner for the task.
Click Add task.

The task is created with the To do status. You can add a description, labels, and linked test cases later from the task’s own view.

Open and Edit a Task

Select a task — either from the Requirements tree or from the parent requirement’s Sub-items tab — to open its detail view.

The task view shows its code, creator, and created date, along with:

Parent requirement — the requirement the task belongs to, shown as a clickable path back up the hierarchy
Title and Description
Owner
Status
Labels

To make changes:

Open the task.
Click Edit Task.
Update the fields you need — including moving the task to a different parent requirement.
Click Save Changes.

Use Cancel to discard your changes and return to the read-only view.

Task Tabs

A task’s detail view includes tabs for the work connected to it:

Testcases — test cases linked directly to the task. While editing, use Add / Update Testcase to change them.
Releases & Testruns — releases and testruns where the task is used.
Defects — defects linked to the task or its test cases.
Comments — discussion on the task.

Tasks do not have a Change History tab or Sub-items tab — those exist only on requirements.

Owner

A task can have an Owner, chosen from the project’s users. Use the Assign me shortcut to make yourself the owner quickly. A task with no owner shows Unassigned.

Assigning an owner also subscribes that person to the task, so they receive updates about it. See Requirement Details for how subscriptions work.

Move a Task

You can move a task to a different requirement by changing its Parent requirement while editing. A task must always belong to a requirement — it cannot be moved to the top level or placed under another task.

Delete a Task

Open the task.
Click Delete.
Confirm in the Delete task dialog.

Deleting a task removes it from its requirement and unlinks it from any test cases. This cannot be undone. Deleting a task does not delete the test cases, releases, executions, or defects it was linked to.

Permissions

Tasks reuse the same project permissions as requirements — there are no separate task permissions:

Creating and editing tasks requires requirement edit access.
Deleting a task requires requirement delete access.

Because tasks are created from the parent requirement’s edit mode, anyone who can edit the requirement can add tasks to it.

Next Steps

Learn about Sub-requirements & Hierarchy
Review the Requirement Details view
Understand where requirements are used