Defect tracking

Defect Statuses:
Defect Status New Assigned Rejected Remark A new defect is opened in the defect tracking tool Defect is assigned to developer for fix Defect is rejected one of the reasons o Duplicate o Not able to reproduce o Not a bug as designed Defect is fixed and code changes are available in the repository Defect is verified in the test server Fix for the defect is not working as expected Developer / QA needs more information on the defect to fix / test in. Defect is confirmed, but will be worked on later release Defect closed

Fixed Verified Reopened NeedInfo OnHold Closed

Defect Life Cycle:

OnHold

New

Assigned

Fixed

Verified

Closed

Need Info

Rejected

Reopened

Defect Status change workflow description:

Defect status change From To New New Assigned Assigned to unassigned Developer Description New defect is opened Dev head assigns it to the developer to fix

New New New

Need Info OnHold Fixed

Reporter unassigned Reporter

New

Rejected

Reporter

OnHold Assigned Assigned

Assigned Fixed NeedInfo

Developer Reporter Reporter / Business Owner / Tech Arch

Assigned

Rejected

Reporter

NeedInfo Fixed Fixed Rejected Rejected Rejected Reopen Reopen

Assigned Verified Reopen Assigned NeedInfo Verified Rejected NeedInfo

Requester Reporter Developer Dev head / Developer Business Owner Reporter Reporter Reporter / Business Owner /

it Dev head requests for more information to reproduce / work on the defect Dev head confirms the defect, but decides to work on it in a later release Defect already fixed (internally found by developer & fixed or got fixed along with another defect) and code changes are available, So Dev head marks as fixed and assigns to the reporter Dev head rejects the defect and assigns to reporter; Reasons o Duplicate o Not able to reproduce o Not a bug as designed Dev head decides to work on the issue and assigns to developer Developer assigns to reporter when defect is fixed and code changes are available in the repository Developer assigns the defect to o Reporter requesting more information to reproduce / work on the defect o Business Owner to confirm on product functionality o Tech Arch to discuss on technical issues / challenges Developer rejects and assigns to reporter; Reasons Duplicate Not able to reproduce Not a bug as designed Require information / comments are provided in the Comments and assigned back to the requester Defect fix is verified in the test environment and status is changed to Verified Fix provided for the defect fails, So reporter assigns it back to the developer who fixed the defect Assignee provided more information supporting the defect and assigns back to Dev head / Developer Assignee request for functionality clarification Assignee confirms the rejection reasons and changes to verified Developer rejects the reopen cause and assigns back to reporter Developer assigns the defect to o Reporter requesting more information to reproduce / work on

Tech Arch

Reopen Verified Closed

Fixed Closed Reopen

Reporter Reporter Developer

the defect Business Owner to confirm on product functionality o Tech Arch to discuss on technical issues / challenges Developer provided additional fix to the reported issue and code changes are made available Defect is verified in the pre-GA build and closed Issue still exists, So reopened to the developer o