 |
| Issues Register Excel Template |
Key Points about the Excel Issues Register
- Simple Excel based template free to download and use.
- Using the template enforces consistency.
- Can be used for Project Issue tracking, Project Defect tracking and Issue Tracking in a team.
- Captures all the key information required for decision making and tracking.
- Contains a summary section which gives a high level view of issues count.
- Conditional formatting to highlight high priority issues.
Fields Excel Issues register
- Sl No - An incremental unique number for each issue.
- Issue Title - A small title for the issue. Examples are "Resourcing Issues", "Login Issue", " Token Issue".
- Issue Description - A detailed description of the issue.
- Reported On and Reported By - Date when the issue was reported and who it was reported by.
- Owner - The person to whom the issue is assigned.
- Severity - Can be one of the following values Critical, High, Medium and Low. Severity of an issue in the measure of the impact that the issue has.
- Priority - Can be Urgent, High, Medium or Low. The Priority defines how fast this issue should be fixed.
- Status - Status can be New, WIP, Closed or On Hold.
- New status should be used when the issue is new and no work has started on it yet.
- WIP is Work In Progress and should be used for issues which are being worked on.
- On Hold status is for issues which have been put on hold for some reason.
- Closed should be used for issues which are fully closed.
- Comments - A free form text field which can be used for variety of reasons. It can be used for adding status updates, mention any road blocks or dependencies.
 |
| Issues Summary |
Tips when using the register
- Update the issues register as soon as the issue is reported.
- You can populate partial information to start with.
- Be sure the correct severity and priority are reported.
- If in doubt then question the information reported.
- Always keep the sheet sorted so that people can find the information they are looking for.
- Book a regular meeting to review the issues register.
- Publish the issues list regularly. If the issues have to be tracked for a short period then you can send it daily. If the project is long then you can publish it weekly.
- The summary section can be pasted directly into the body of the email which will be used to publish the issue register.