Bug Log
Company: [YOUR COMPANY NAME]
Company Number: [YOUR COMPANY NUMBER]
Address: [YOUR COMPANY ADDRESS]
Bug Details
Bug ID | Description | Severity | Status | Reported Date |
|---|
001 | Application crashes on login | Critical | Open | August 15, 2050 |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
Prioritization Criteria
To effectively prioritize the fixes, we use the following criteria:
Severity: Assess the impact of the bug on the application's functionality and user experience.
Frequency: Determine how often the bug occurs and how many users are affected.
Reproducibility: Evaluate how consistently the bug can be reproduced.
Business Impact: Consider the potential impact on revenue, compliance, or critical business operations.
Effort Required: Estimate the time and resources needed to resolve the bug.
Prepared by: [YOUR NAME]
Email: [YOUR EMAIL]
Log Templates @ Template.net
