Templates

This page mainly explains about the the common templates that we need to follow for all the projects in HPRO.

Most of the teams are following most of it ,but this definition can help to get all projects to uniformly follow the common ways of creating issues.

Defect Template
Below is the defect creation template that is proposed to follow across all the project.

Some Notes:

Components - This field is mandatory as this will help in filtering the defects easily based on components. (Will check with JIRA team if
this can be made mandatory)
AffectsVersion/s - This field is mandatory, this will help in analyzing the defects based on each version. (Will check with JIRA team if
this can be made mandatory)
Linked issues - Linking a defect could help in easy search of test case associated, User story or task that is associated. This will help us
in building the traceability matrix.

Test case template

 Note: In case if you have multiple ways to check a particular test
please add in the steps as Case 1:, Case 2:

Some Notes:

Components - This field is mandatory as this will help in filtering the defects easily based on components. (Will check with JIRA team if
this can be made mandatory)
AffectsVersion/s - This field is mandatory, this will help in analyzing the defects based on each version. (Will check with JIRA team if
this can be made mandatory)
Linked issues - Linking a defect could help in easy search of test case associated, User story or task that is associated. This will help us
in building the traceability matrix.

Test case Review Template