Skip to main content
Requirements represent the things your software must do — user stories, features, epics, tasks, and bugs. Linking requirements to test cases is how Orizon builds the coverage matrix and tells you which parts of your product are tested.

​
Requirement fields

Each requirement has the following fields:
FieldDescription
KeyA unique identifier, auto-generated from the title (e.g., REQ-LOGIN-EMAIL). Immutable after creation.
TypeOne of: Story, Epic, Bug, Feature, Task
TitleA short description of the requirement
DescriptionDetailed explanation of the requirement
StatusOne of: Open, In Progress, Done, Cancelled
PriorityOne of: Critical, High, Medium, Low
VersionOptional — a version tag or sprint label (e.g., v1.0, Sprint 42)
External IDOptional — an ID from an external system (e.g., JIRA-123, AZ-456)
External URLOptional — a direct link to the external system’s issue page

​
Creating a requirement manually

1

Open your project's requirements list

Navigate to your project, then click Requirements in the project sidebar.
2

Click New Requirement

Click the New Requirement button in the top-right corner.
3

Fill in the form

The requirement key is auto-generated from the title as you type — you can override it. Set the type, status, priority, and optionally a version and external reference.
4

Save

Click Create Requirement. You land on the requirement detail page where you can link test cases.

​
Importing from an integration

If your project is connected to GitHub, GitLab, or Azure DevOps, you can sync issues directly as requirements.
1

Connect the integration

Go to your project’s Settings → Integrations and connect your provider. See Integrations for the full setup steps.
2

Trigger a sync

Once connected, trigger a manual sync from the integrations settings page. Orizon fetches all issues from the connected repository and creates or updates requirements automatically.
3

Stay in sync with webhooks

After the initial sync, configure webhooks so that new issues and issue updates flow into Orizon in real time. See Webhooks for details.
Synced requirements include the external ID and a direct link back to the original issue. Orizon uses the external ID to avoid duplicates — re-syncing updates existing requirements rather than creating new ones.

​
Importing generated requirements from an analysis

When you run a codebase analysis, Orizon can generate user stories and acceptance criteria alongside test cases. You can import those directly into a project:
1

Run a codebase analysis

Go to Generate and run an analysis with user stories enabled. See Codebase Analysis for setup.
2

Import into a project

After the analysis completes, use the Import option to send the generated requirements and test cases into an existing project. Orizon creates requirements and links the corresponding test cases automatically.

​
Filtering and sorting

On the requirements list page you can:
  • Search by title, key, or description
  • Filter by type (Story, Epic, Bug, Feature, Task), status, or priority
  • Sort by date created, title, priority, status, or type
The stats bar at the top of the list shows total, open, in-progress, and done counts for the current view.

​
Linking to test cases

Open a requirement’s detail page to see all test cases linked to it. Click Manage Coverage → to go directly to the coverage matrix filtered for that requirement, where you can add or remove links.
Requirements with a Critical or High priority and zero linked test cases show up highlighted in the Coverage Gaps view — a quick way to prioritize what to test next.