Skip to main content
A project is the top-level container for all your QA work in Orizon. Each project holds requirements, test cases, test runs, defects, and the coverage matrix that ties them together. You can connect a project to GitHub, GitLab, or Azure DevOps to sync issues and receive CI/CD events automatically.

​
Key concepts

Every project follows the same structure:

Requirements

User stories, epics, and features that define what your software must do.

Test Cases

Step-by-step tests that verify your requirements are met.

Coverage Matrix

A traceability view showing which requirements have tests and which don’t.

Integrations

Connect GitHub, GitLab, or Azure DevOps to sync issues and test results.
The typical workflow is:
  1. Create a project and optionally link an integration
  2. Add requirements — manually or by syncing from your issue tracker
  3. Create or import test cases and link them to requirements
  4. Use the coverage matrix to find gaps and track progress

​
Creating a project

1

Open the Projects list

Navigate to Projects in the sidebar and click New Project.
2

Fill in the project details

Provide the following information:
FieldRequiredDescription
NameYesA descriptive name (e.g., My E-Commerce Project)
KeyYesA 2–10 character uppercase identifier (e.g., ECOM). Auto-generated from the name — you can edit it. The key is permanent once the project is created.
DescriptionNoOptional context to help teammates understand the scope
The project key is used as a prefix for all requirements and test cases in this project (e.g., ECOM-REQ-1, TC-42). It cannot be changed after creation.
3

Create the project

Click Create Project. You land on the project overview page.
Once inside a project, the sidebar expands to show all project sections. The project overview page gives you at-a-glance metrics:
  • Health score — A 0–100 score derived from pass rate, coverage, and open defects
  • Pass rate — Percentage of test runs that passed
  • Coverage — Percentage of requirements that have at least one linked test case
  • Test Cases — Total count, with a breakdown of how many are ready
  • Requirements — Total count
  • Test Runs — Total runs, with active runs highlighted
  • Defects — Total count, with open defects highlighted
  • Sprints — Sprint tracking (if configured)
The Quick Actions panel on the overview page lets you jump directly to common tasks: generate tests with AI, create a test case, add a requirement, start a test run, report a defect, or open agent tests. The project dashboard (accessible from the sidebar) shows charts for requirements by status, tests by status, defects by severity, and an activity trend for the last 7, 14, 30, or 90 days.

​
Project list

The Projects list at /projects shows all your projects with summary health metrics. You can:
  • Search by project name, key, or description
  • Sort by last updated, name, health score, most defects, or most tests
  • Filter between Active, All, and Archived projects
The KPI bar at the top of the list shows totals across all active projects: active project count, average health score, total open defects (with critical defect count), and average coverage percentage.
Sort by Health (worst first) to immediately surface the projects that need the most attention.