QA: Defect logging guideline

The objectives of defect logging guideline are:

• To standardize QA guideline for defect logging in JIRA.
• To ensure QA provides enough information for defect logging in JIRA to support developer to investigate issue effectively.
• To utilize issue tracking system applied to the work.
• To support information to collect statistics for Test Matrix.

Defect logging guideline can be separted into:

• Guideline to open JIRA issue
• Guideline to resolve JIRA issue
• Guideline to reopen JIRA issue
• Guideline to close JIRA issue

Guideline to open JIRA issue

Field	Description	Require Field?	Guideline	Example
Issue Type	Classify issue type: - Bug: Problem which impairs or prevents the functions of the product. - Task: Task that needs to be done, or question regarding of the system. - Improvement: Improvement/enhancement to an existing feature or task, or improvement for system stability/performance. - New Feature: A new feature of the product, which has yet to be developed.	Yes	- Bug - Task - Improvement - New Feature	Bug
Summary	Summary of issue	Yes	[Module] – [Screens/Functions]: Summary of issues	[Product] - [Proposal Entry]: An error "Code: NB1510 There was an error validating the product details: The entered term or age of the client is invalid., Plan Validation Failed.." message displays
Test Phase	Define test phase	Yes	- None - SIT - UAT	SIT
Component/s	Components associated with the issue	Yes	- All - CLM - CMS - FIN - NB - NB-UW - POS - PRD - PS - RI - UW	PRD
Priority	Priority signifies how important and urgently it is to fix this defect. - Blocker o Blocks development and/or testing work, production could not run. o A problem that stops a user from using software or causes unacceptable interruption to work without workaround. - Critical o Crashes, loss of data, severe memory leak. o A problem affecting the usage of software with temporary workaround or limited impact. o Crashes when doing specific operations, which does not affect other usage of the product or existing workaround for systematic crashes. o Some testing can continue. - Major o Major loss of function. o A single user or a set of users is impacted from doing a certain task under certain conditions. - Minor o Minor loss of function, or other problem where easy workaround is present. o A single user or a set of users is impacted from doing a certain task under certain conditions. - Trivial o Cosmetic problem like misspelled words or misaligned text.	Yes	- Blocker - Critical - Major - Minor - Trivial	Blocker
Product Code	Specific Product Code	No		ORD0147-ซีเนียร์ แฮปปี้2
Test Set ID	Specific Test Set ID	No		ORD_P0313
Test Case ID	Specific Test Case ID	No		PD-TC-001
Assignee	Specific assignee to take action	Yes	Test Lead	Test Lead
Attachment	Attachment/screenshot	Yes		CIT-133.jpg
Test Environment	Test environment associated with the issue	Yes	- SIT Env 1 - SIT Env 2 - UAT Env 1 - UAT Env 2	SIT Env 1
Test Category	Categorize area of issue	Yes	- Master - Functional - Batch Process - Interface - Report and Letter - Non Functional - Pre-SIT	Functional
Affect Version	Software version associated with the issue	Yes	X.X.X	8.10.0
Description	Description of issue	Yes	Pre-requisite (if needed) 1. 2. 3. Steps to reproduce 1. 2. 3. Test data ... Actual results … (See attachment; xx.jpg) Expected results …	Pre-requisite 1. Product information configures completely; e.g. Product Code: ORD0147-ซีเนียร์ แฮปปี้2. 2. Agent information configures completely; e.g. Agent = 200014. Steps to reproduce 1. Login to the system. 2. .. Test data - Product Code: ORD0147 - Agent: 200014 Actual results When user submits "Proposal Entry" form, an error "Code: NB1510 There was an error validating the product details: The entered term or age of the client is invalid., Plan Validation Failed.." message displays. (See attachment; CIT-133.jpg) Expected results User should be able to submit "Proposal Entry" form without getting error.

 

Guideline to resolve JIRA issue

Field	Description	Require Field?	Guideline	Example
Fixed Version	Software version associated with the resolved issue	Yes	X.X.X	8.11.1
Resolution	Resolution of resolved issue: - Fixed: A fix for this issue is checked into the tree and tested. - Won't Fix: An issue which will never be fixed. - Duplicate: Duplicate of an existing issue. - Incomplete: The problem is not completely described. - Rejected: Cancel or reject issue - On Hold: An issue is on hold. - Cannot Reproduce: All attempts at reproducing this issue failed, or not enough information was available to reproduce the issue. - Done	Yes	- Fixed - Won't Fix - Duplicate - Incomplete - Rejected - On Hold - Cannot Reproduce - Done	Fixed
Issue Category	Specific root cause of issue: - Application - Data - Environment - Tester/User - Inquiry - Requirement - Other	Yes	- Application - Data - Environment - Tester/User - Inquiry - Requirement - Other	Application
Assignee	Specific assignee to take action	Yes	Test Lead	Test Lead

Guideline to reopen JIRA issue

Field	Description	Require Field?	Guideline	Example
Comment	Specific comment for reopen issue	Yes	Reopen this issue on Software Version [X.X.X]. Pre-requisite (if needed) 1. 2. 3. Steps to reproduce 1. 2. 3. Test data ... Actual results … (See attachment; xx.jpg) Expected results …	Reopen this issue on Software Version 8.12.0. Pre-requisite 1. Product information configures completely; e.g. Product Code: ORD0147-ซีเนียร์ แฮปปี้2. 2. Agent information configures completely; e.g. Agent = 200014. Steps to reproduce 1. Login to the system. 2. .. Test data - Product Code: ORD0147 - Agent: 200014 Actual results When user submits "Proposal Entry" form, an error "Code: NB1510 There was an error validating the product details: The entered term or age of the client is invalid., Plan Validation Failed.." message displays. (See attachment; CIT-133.jpg) Expected results User should be able to submit "Proposal Entry" form without getting error.
Assignee	Specific assignee to take action	Yes	Test Lead	Test Lead
No. of Reopen Time	No. of reopen times for fix issue   Remark Manually increase by 1 when reopen fix issue.	Yes	[Numeric]	1

Guideline to close JIRA issue

Field	Description	Require Field?	Guideline	Example
Comment	Specific comment for reopen issue	Yes	Close this issue on Software Version [X.X.X].	Close this issue on Software Version [8.12.0].
Assignee	Specific assignee to take action	Yes	Reporter	Reporter