An issue Log is a collection of issues raised in a context of or team, and tracking their status. It is a part of a project management. An issue log contains a list of ongoing and closed issues of the project. Issue logs can be used to order and organize the current issues by type and severity in order to prioritize issues associated with the current project. An issue log is usually blank at the beginning of the project, where it will be filled with issues once people found a problem in their project where they cannot solve it directly. In some cases, the issue log is being used as a guideline for the release schedule; in that case the issue log can be populated with issues that are specifically tagged to be finished in certain dates or time. As a result, issue log-guided projects may be easier to manage in terms of completion time and progress estimation. In large projects, issues are usually managed by issue tracking software that can provide different ways and tools to help the project manager and the development team handle thousands of issues for one or several of their projects.
This issue log template below should give you ideas about creating your own issue log based on your projects. There are nine columns with title as follows: Issue No (used as your issue reference), Issue Description, Responsible (people who responsible on solving issues), Reported Date (the first date when the issue is found), Action (action taken to solve the issue, it could be more than one solution), Action Date, Due Date (this is a deadline), Priority, and Status (open, close or pending). You can add more columns or eliminate some columns. You can also change the titles with titles that is more relevant with your ongoing projects.
Issue Log Template (49.5 KiB, 1,350 hits)