In a typical issue log, the document must be a table containing multiple rows in which each row describes a separate issue. The various attributes of the issue are listed in different columns. An example of a typical issue log is shown below.
Basic issue information •
Issue reference number (ID): Typical number to identify different issues. •
Issue name: Issue's name. •
Description: Briefly describe what the issue concerns. •
Issue author: The person who raise this issue. •
Parties: all the people involved in solving the issue.
Issue categories •
Issue type: what knowledge domain the issue belongs to. (E.g. IT infrastructure, IT application, etc.) •
Issue priority: it determines which issue is the most urgent and should be solved first. (E.g. the priorities may encompass Immediate, Soon, Later, etc.) •
Issue severity: how bad the consequence would be if the issue is left unsolved. (E.g. the severity may encompass Vital, Major, Medium, Minor, etc.)
Issue date information •
Date raised: when the issue is raised. •
Date assigned: when the issue is assigned. •
Deadline: when is the final date to get the issue settled. •
Date resolved: when the issue is actually solved.
Issue status •
Current status: the current status the issue is within. (e.g. investigating, escalated, resolved, etc.) •
Actions updating: Actions performed before issue is resolved (List all the actions according to dates.) •
Resolution: The final resolution to settle the issue.
Other information •
Notes: Some ideas or things to remember. The documentation style of an issue log may differ from project to project. Some of attributes listed above may be considered unimportant to record, while other additional attributes may be necessary. However, main attributes such as description, author, priority, status, and resolution should always be included. Further, the sequence of attributes may differ as well. ==See also==