Requirements

Requirements keep product work aligned with testing. Use them to track epics, user stories, features, or tasks and maintain end-to-end traceability.

Creating a requirement

Each requirement can include:

• Title & rich description – Capture acceptance criteria, background, and assets using the TipTap editor.
• Form – Categorise as epic, user story, feature, or task.
• Workflow state & status – Map where the requirement sits in your process (Draft, In Progress, In Review, Done, etc.). Workflow states are fully customisable per project.
• Priority & severity – Indicate business impact and urgency.
• Assignee & reporter – Track ownership; changes send notifications.
• Milestone & due date – Align work with release timelines.
• Parent requirement – Build hierarchies for epics and child stories.
• Tags – Add thematic labels for filtering and analytics.
• Attachments – Upload design files, screenshots, or documents.

Traceability

• Link tests – Associate requirements with internal test cases. Coverage widgets highlight how many approved tests exist and whether they have recent executions.
• External references – Link external tickets (Jira, ClickUp, GitHub) via external links. Search and link requirements from integrated systems manually.
• Run impact – When a test run references a linked test case, requirement analytics show execution status and outstanding defects.

Working the board

• View requirements on a kanban board grouped by workflow state.
• Drag cards to update their position and column; the order is stored for prioritised backlogs.
• Filter by assignee, milestone, priority, tag, or status to focus on a subset.

Best practices

• Keep descriptions concise but actionable—add acceptance criteria and links to UX or API specs.
• Use parent/child relationships to roll up release readiness (e.g., 100% child stories tested before an epic is marked done).
• Pair requirement status changes with review workflows so QA can verify test coverage before work closes.