Glossary Term	Description
Description	A comprehensive detail of the issue to provide a reader with full understanding of the issue. This should include any information relevant to the issue such as the specifics associated with it, how it is identified and the members it may affect.
Department	Issues are filtered by department within the program
End Date	The planned date when the Issue will be resolved and closed. The issue will be escalated if the due date has passed.
Issue Details	A brief description of an issue. This should include any information linked to the specifics of the source, purpose and impact of the issue. This allows users to document and track an issue. Thus, an issue can be effectively reviewed and mitigated at any point in time.
Issue ID	Unique identifier generated and assigned to an Issue when created and saved.
Issue Name	A short title which outlines the issue and its impact. The name should incorporate 3 pieces of information which are the 'what', the 'how' and the 'impact' of the issue.
Issue Register	A Issue Register serves as a repository for all identified issues. Any information pertaining to an issue is added to the register. This may include the nature, owner and actions to resolve each issue.
Issues	An issue is an unplanned event or a risk which has materialised that, without action, will negatively impact the project(s) scope, cost, quality, and/or schedule.  Issue Management is the process of identifying, tracking and taking corrective measures to resolve the issue to minimise impact to project
Next Review Date	The date allocated for a subsequent review of the issue. This helps monitor the issue and manage any critical problems that may arise.
Opportunity Detail	A brief description of an issue. This should include any information linked to the specifics of the source, purpose and impact of the issue. This allows users to document and track an issue. Thus, an issue can be effectively reviewed and mitigated at any point in time.
Owner	The project member who is responsible for managing the issue. The owner of the issue is required to have a thorough understanding of the issue. This is essential for mitigating the impacts of the issue.
Participants	The key people involved  to assist owner with the management of the issue.
Priority	The priority assigned to an issue: Low- Issue has little to no impact on the project deliverables, regular monitoring required Medium- Issue has a moderate impact on the project and a remedial plan to be implemented as soon as possible, regular monitoring required High- Issue is critical and has major impact on the project, immediate action and active management is required.
Raised By	Name of user who identified and logged the issue.
Resolution Details	An overview of the proposed issue resolution, owner and expect date to be resolved.
Resolution Plans / Actions	A summary of the issue resolution plan. This should include information on how and when it will be implemented. Details of the resources required to execute the resolution plan should also be included here.
Risk Links	List of any risks linked to the issue. An issue can either be created from a risk or automatically assigned to a risk.
Start Date	Date automatically populated based on 'today' when issue created and saved
Status	Current status of the issue: Pending approval- The issue has been raised and pending approval by Approver Approved – Issue has been approved and being monitored Rejected- Issue has been rejected by Approver Resolved- Issue has been closed
Workstream	Workstreams are core areas of activities in your project. Could be a department in your organisation (i.e Operations or Marketing) or an ongoing activity in your project (i.e Testing or Implementation).