Page History
...
You can use a single project to manage your Requirements and Defects, Test-related issues as well as all your Test Executions.
| Info | ||
|---|---|---|
| ||
This is the preferred organization approach as it provides some key benefits over other alternatives:
|
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
Don't mix my Requirements and Defects with Tests
...
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
Dedicated repository for Tests
...
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
| Tip | ||
|---|---|---|
| ||
If you plan to have separate projects for managing Requirements/Defects and Tests Executions and you want to analyze Requirements by version, then your Requirement's project version names must match the names of the Test Execution's project. This is how to do it. |
...
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
Isolated repository for Tests
...
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
| Info |
|---|
Users implementing this scenario might gain huge benefits if they are able to synchronize requirements between the other tool and Jira. |
...