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 | ||||
---|---|---|---|---|
|
How to set it up
- Create a new Scrum project or use an existing one.
- Add Test, Precondition, Test Set, Test Plan, Test Execution and Sub-Test Execution issue types to the project. This can easily be done using a shortcut available in the Summary section within the project settings (see Project Settings: Summary) for editing the Issue Type Scheme used by the project. You can also be do it from within Jira administration > Settings > Issues > Issue Type Schemes.
- In the project settings, within the Test Coverage section (see Project Settings: Test Coverage), define the Covered Issue Types (i.e., the testable entities such as the typical requirements, user stories, epics). On the left side, you can see all available Issue Types. Drag the ones you want (e.g., Story, Epic) to the Covered Issue Types and save the settings.
...
Gliffy Diagram | ||||
---|---|---|---|---|
|
How to set it up
- Create a Scrum project or use an existing one for managing the "Requirements Project".
- Create another project (it can also be a Scrum project) for managing the "Test Project".
- In the "Test Project", add Test, Precondition, Test Set, Test Plan, Test Execution and Sub-Test Execution issue types to the project. Remove all other issue types. This can easily be done using a shortcut available in the Summary section within the project settings (see Project Settings: Summary) for editing the Issue Type Scheme used by the project. You can also be do it from within Jira administration > Settings > Issues > Issue Type Schemes.
- In the "Requirement Project" project settings, within the Test Coverage section (see Project Settings: Test Coverage), define the Covered Issue Types (i.e. the testable entities such as the typical requirements, user stories, epics). On the left side, you can see all available Issue Types. Drag the ones you want (e.g., Story, Epic) to the Covered Issue Types and save the settings.
...
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. |
How to set it up
- Create a Scrum project or use an existing one for managing the "Requirements Project".
- Create another project (it can also be a Scrum project) for managing the "Test Project"
- Create another project (it can also be a Scrum project) for managing the "Test Executions Project".
- In the "Test Project", add Test, Precondition and Test Set issue types to the project. Remove all other issue types. This can easily be done using a shortcut available in the Summary section within the project settings (see Project Settings: Summary) for editing the Issue Type Scheme used by the project. You can also be do it from within Jira administration > Settings > Issues > Issue Type Schemes.
- In the "Test Executions Project", add Test Plan, Bug and Test Execution issue types to the project. Remove all other issue types.
- In the "Requirement Project", add the Sub-Test Execution issue type.
- In the "Requirement Project" project settings, within the Test Coverage section (see Project Settings: Test Coverage), define the Covered Issue Types (i.e., the testable entities such as the typical requirements, user stories, epics). On the left side, you can see all available Issue Types. Drag the ones you want (e.g., Story, Epic) to the Covered Issue Types and save the settings.
...
Gliffy Diagram | ||||
---|---|---|---|---|
|
How to set it up
- Create a Scrum project or use an existing one for managing the "Requirements Project".
- Create another project (it can also be a Scrum project) for managing the "Test Project".
- Create another project (it can also be a Scrum project) for managing the "Test Executions Project"
- Create another project (it can also be a Scrum project), for managing the "Defects Project".
- In the "Test Project", add Test, Precondition and Test Set issue types to the project. Remove all other issue types. This can easily be done using a shortcut available in the Summary section within the project settings (see Project Settings: Summary) for editing the Issue Type Scheme used by the project. You can also be do it from within Jira administration > Settings > Issues > Issue Type Schemes.
- In the "Test Executions Project", add Test Plan and Test Execution issue types to the project. Remove all other issue types.
- In the "Requirement Project", add the Sub-Test Execution issue type.
- In the "Defects Project", add the Bug issue type.
- In the "Test Executions Project", add Test Plan and Test Execution issue types to the project. Remove all other issue types.
- In the "Requirement Project" project settings, within the Test Coverage section (see Project Settings: Test Coverage), define the Covered Issue Types (i.e., the testable entities such as the typical requirements, user stories, epics). On the left side, you can see all available Issue Types. Drag the ones you want (e.g., Story, Epic) to the Covered Issue Types and save the settings.
...
Gliffy Diagram | ||||
---|---|---|---|---|
|
Info |
---|
Users implementing this scenario might gain huge benefits if they are able to synchronize the requirements in the other tool and Jira. |
...