The document discusses ETS's defect management process in Jira, including how to create and manage different types of defects for issues identified during testing or in production environments, and how defects should be linked to user stories to track resolution. Defects refer to problems or errors, while enhancements are additional features or functionality, and defects should be prioritized based on their severity and impact.
The document discusses ETS's defect management process in Jira, including how to create and manage different types of defects for issues identified during testing or in production environments, and how defects should be linked to user stories to track resolution. Defects refer to problems or errors, while enhancements are additional features or functionality, and defects should be prioritized based on their severity and impact.
The document discusses ETS's defect management process in Jira, including how to create and manage different types of defects for issues identified during testing or in production environments, and how defects should be linked to user stories to track resolution. Defects refer to problems or errors, while enhancements are additional features or functionality, and defects should be prioritized based on their severity and impact.
The document discusses ETS's defect management process in Jira, including how to create and manage different types of defects for issues identified during testing or in production environments, and how defects should be linked to user stories to track resolution. Defects refer to problems or errors, while enhancements are additional features or functionality, and defects should be prioritized based on their severity and impact.
Download as DOCX, PDF, TXT or read online from Scribd
Download as docx, pdf, or txt
You are on page 1/ 4
ETS Defect Management Process (Basic)
Why do we need to raise a Defect? What is the difference between Defects and Enhancements? A mistake that has been made in the Defect is the problem or error found in the past, but for some reason it was not application while testing, postproduction or detected. which may have negative impact to the Manifestation of technical debt in your other functions of the application. system and they may be directly visible Enhancement is the additional feature or to your customer, which usually has a big functionality found and added to the impact on the priority. application as desired by the end user/real Any issue or error identified during word customer or tester during the testing Peer/User and Business testing. process.
What are the different types of Defects? How to manage Defects Vs Enhancements in JIRA? For managing defects create Jira Issue type Production – Any defect/errors resulted as “Defect” or identified after the production release. For enhancements create a Jira issue type as o Choose Environment type as “Story”. “Production” in Jira Non-Production (Dev, QA, Staging): Any defects/errors identified during peer/user or Business testing before they gets implemented in Production environment. Choose Environment type as “Staging/ Development/ Demo” in Jira
Defect Management in JIRA
Create a Non-Production Defect
1. Assuming you are inside your JIRA
project, click on “Create” 2. Select Issue type as “Defect” 3. Enter summary about the defect as shown in the screenshot. 4. Enter the exact defects identified during the testing or after production releases. a. This could be one of the functionalities from many delivered through the Story.
5. Enter specific acceptance criteria
which functionality/features will be subsequently tested during defect closure.
6. Select the correct environment type
depending on when the defect has been identified. a. Ex: if the defect has been identified during UAT, Peer Testing, then select “Demo or Staging or Development” b. Ex: if the defect has been reported by user or proactive alerts in Production, select “Production” as type.
7. Fill addition mandatory information:
a. Assignee (Team member, preferably who developed it) b. Reporter (User/BA/Peer) c. Story Point (1 SP = 1 Hour) d. Sprint (Note: if the defect is production + critical, then it has to be addressed in current sprint) e. Priority (Severity + Impact) Create a Production defect If the defect has resulted out of an already deployed feature/product, it may come through a ServiceDesk ticket, Email or SFDC case. o You can directly create a defect in JIRA and copy issue-related information from one of the above-mentioned sources (OR) o Convert the ServiceDesk ticket to JIRA issue (Please check if SNOW ticket can be converted to JIRA issue type = Defect) Note: Production defects mostly take priority over non-Production defects.
Defect and Story linkage
OPTION-1 – Non-Production defect 8. If it is a Non-Prod Defect and resulted during UAT/Peer testing, a. Go to the story which generated this defect. b. Click “Link issue” as shown. This will scroll you down to Linked issue
9. Type few characters/words of the
defect title or defect Number. a. Matching list will appear b. Select appropriate defect from the list 9.1. A defect can be created directly from the story: Click on the “Create Linked issue” Follow step # 2 to #7
10. Select “is blocked by” from the drop
down. 11. Click “Link” to link the defect with story. Once you link the defect with Story, this is how the linked issue will appear in both “Defect” and “Story” This can be easily tracked in future.
