The document describes the typical lifecycle of a software bug, from when it is first reported as a new bug to when it is eventually closed once fixed. The lifecycle involves the bug changing states as it is reviewed, assigned to a developer, tested after a fix is applied, and finally closed once fully resolved. The document also outlines the different levels of severity a bug can be classified as, from critical bugs that prevent testing to minor cosmetic bugs, and provides an example of a bug report template.

1. Bug Life Cycle

19. BUG REPORTING

20. Issue Type: Code Defect, Spec issue, Test Data How Found: Ad Hoc, Scorecard – Post check-in, Other Severity: 1 – causes system crash or data loss; 2 – Causes major functionality or severe problem; 3 – Causes minor functionality problem; 4 – Typos, unclear wording or error message Priority: 1 – Must fix in this milestone; 2 – Must fix by next milestone or prior to RTM; 3 – Should fix, but could ship without. Feature ID & Name 12080-Reason Codes Setup Bug Title Reason label is incorrect Build 5.0.392.0 Issue Type Code defect How Found TCS Execution Severity 3 Priority 1 Repro Steps Open Accounts Receivable > Setup > Customer Reasons Click on Overview tab. Verify that Overview tab contains ‘Reason’ and Default Comment fields Expected Result ‘ Reason code’ field is displayed Actual Result ‘ Reason’ field should be displayed Click on General tab. Verify under Identification field group there are fields Reason and Default Comment Expected Result ‘ Reason code’ field is displayed Actual Result Reason field should be displayed