Requirements Overview

Requirements track business needs and how your project addresses them.

What are Requirements?

Requirements represent:

• Business needs and objectives

• Functional requirements

• Technical specifications

• Compliance needs

• User stories

Viewing Requirements

1

Requirements List

Navigate to All Requirements or view them within a project:

• Open a project

• Go to the Requirements tab

2

Requirement Details

Each requirement shows:

• Title and description

• Status (Fit, Gap, Partial)

• Priority

• Linked test cases

• Linked issues

• Comments

Creating Requirements

Add a Requirement

1

• Open a project

• Go to the Requirements tab

• Click + New Requirement

• Fill in the details:

  • Title – Brief name

  • Description – Full requirement text

  • Status – Fit, Gap, or Partial

  • Priority – Importance level

  • Category – Type of requirement

• Click Create

Import from Excel

1

• Click Import

• Download the template

• Fill in your requirements

• Upload the completed file

• Review and confirm the import

Fit/Gap Analysis

Requirements can be marked with their implementation status:

Status	Meaning
Fit	The system meets this requirement
Gap	The system does not meet this requirement
Partial	The system partially meets this requirement
Not Evaluated	Not yet assessed

Updating Status

1

• Open the requirement

• Click the status dropdown

• Select the appropriate status

• Add notes explaining the assessment

Linking Requirements

Link to Issues

1

When a gap is identified:

• Open the requirement

• Click Link Issue

• Create or select an issue

• Track issue resolution

Link to Tasks

1

Connect implementation tasks:

• Open the requirement

• Click Link Task

• Select related tasks

• Track completion

Requirement Comments

1

Discuss requirements with your team:

• Open the requirement

• Scroll to comments

• Add questions, clarifications, or updates

• @mention team members

Editing Requirements

1

• Open the requirement

• Click Edit

• Update any field

• Changes save automatically

Deleting Requirements

1

• Open the requirement

• Click the ... menu

• Select Delete

• Confirm deletion

Note: This removes linked test cases and cannot be undone.

Requirements History

1

• Open the requirement

• Click History

• See all changes with timestamps

• Track who made what changes

Best Practices

Writing Requirements

• Be specific and measurable

• Use consistent terminology

• Include acceptance criteria

Fit/Gap Analysis

• Review all requirements systematically

• Document reasons for each status

• Update as the project progresses

Test Coverage

• Create test cases for critical requirements

• Ensure gaps have tests for verification

• Execute tests regularly