Scribd
Upload
2K views

Defect Tracking Log TEMPLATE

The document is a defect tracking log for a [ProjectName] that contains information about issues found during the software development lifecycle (SDLC). It includes details like the problem ID, date opened, system affected, description, priority, root cause, phase introduced, and status. The log has sections for initiation details, resolution details, and a status tracking table.

Uploaded by

Rev. Mark Ray Robinson
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as XLS, PDF, TXT or read online on Scribd
2K views

Defect Tracking Log TEMPLATE

The document is a defect tracking log for a [ProjectName] that contains information about issues found during the software development lifecycle (SDLC). It includes details like the problem ID, date opened, system affected, description, priority, root cause, phase introduced, and status. The log has sections for initiation details, resolution details, and a status tracking table.

Uploaded by

Rev. Mark Ray Robinson
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as XLS, PDF, TXT or read online on Scribd
You are on page 1/ 2

Company Name

LOGO

[ProjectName] Defect Tracking Log

Initiation
SDLC Stage Defect Found

Discovery Impact Assessment


Measure of Impact to Bus Area (quantitative or qualitative)

Resolution
Root CauseCorrected? Status Retested?How?

Problem ID Number

Date Opened

System / Component

Description

TS# / PR#

Found by

Assigned to

Priority/ Severity

Description of Impact

Root Cause of Problem

Phase Defect Introduced

Action Items

Last Status Date

Page 1 of 2

LOGO

Company Name
Defect Tracking Log

Defect Status SUBMITTED OPEN DEFERRED DISAPPROVED APPROVED ASSIGNED FIXED/CODED RETEST CLOSED RESUBMIT REFERRED
SDLC Stages Found Analysis Design Construction Testing - Performance Testing - System Testing - UAT Testing - Sys/UAT Testing - Staging Implementation Production Post Production Verification Other

The problem/issue has been submitted. No further action has been taken, as yet. The problem/issue has been verified by a test coordinator and is ready for review. The problem/issue has been deferred to a future release. The Response team disapproves the problem/issue (e.g. duplicates). The Response team agrees this is a legitimate issue, and has assigned a Technical team to resolve the issue. The Technical Team lead has assigned one or more individuals to resolve the issue. The problem/issue has been resolved and the code is ready for a build/move to System test. A problem has been fixed and released/moved into the Test environment; it is ready for the Shakeout test and then retest and verification. The fix has been retested and accepted. The fix is not accepted; the defect is returned to the Tech team for resolution. The problem/issue has been referred to Change Request Source of Defect
Planning Analysis Design Construction Testing Implementation Post Prod Verification Production

Defect Priority 1 2 3 4 Status


1 2 3 4 5 6 7 8 9 20 21

Ext High High Medium Low

Submitted Open Approved Assigned Resubmit Fixed/Coded Retest Referred to CC Deferred Closed Disapproved

You might also like