In Jira, all information is organized into projects. The way those projects are organized changes from company to company.
Projects in Jira are more likely to represent products or projects (real projects), but is also common to have projects per team or even per process area (like maintenance).
Concerning Xray, you can have different approaches to project organization and they will need different configurations efforts.
Keep requirements, tests and defect in the same project - The All-in-One approach
You can use a single project to manage your Requirements and Defects, Test-related issues as well as all your Test Executions.
To enable this approach you need to perform the following actions as an admin:
| Create Project |
You may not need to create a new project. You can simply add Xray Types to our existing project |
|---|---|
| Enabling Requirement Coverage |  |
| Enabling Xray Issue Types | |
| Project Scope | Single project that is a Requirement Project & a Test Project at the same time |
The All-IN-One approach is the simplest and is the one suggested during the Basic Setup.
Most organizations use this simple approach!
Don't mix my Requirements and Defects with Tests
If you already have a Jira project for managing Requirements and Defects and don't want to have any tests nor executions in this project, you can create a separate companion project just for testing purposes.
To enable this approach you need to perform the following actions as an admin:
| Create Project |
Create a Project for Testing Purposes |
|---|---|
| Enabling Requirement Coverage | At Requirement Project |
| Enabling Xray Issue Types | At Testing Project |
| Project Scope | 1 Requirement Project 1 Testing Project |
Dedicated repository for Tests
Another common use case for Xray is to have a dedicated project for Test (and Pre-Condition and Test Set) issues. Test Executions are the responsibility of other project(s). This separation allows you to manage permissions more effectively, so maybe only a few testers have permission to write tests and others only have permission to execute.
Of course, this use case can also be combined with the previous one by having separate projects for managing Requirements and Defects.
To enable this approach you need to perform the following actions as an admin:
| Create Project |
Create 1 Project with Tests Create 1 Project with Test Executions |
|---|---|
| Enabling Requirement Coverage | At Requirement Project |
| Enabling Xray Issue Types | At 2 Testing Projects |
| Project Scope | 1 Requirement Project 2 Testing Project |
Completely separate
In this use case, the Tests, Requirements, Executions & Plans and Defects all separated and being handled on different projects.
| Create Project |
Create 1 Project with Tests Create 1 Project with Test Executions Create 1 Project for Defects |
|---|---|
| Enabling Requirement Coverage |
Optionally, you can enable also at Defects Project |
| Enabling Xray Issue Types | At 2 Testing Projects |
| Project Scope | 1 or 2 Requirement Project 2 Testing Project |