Change Log Vs Issue Log

Lenin

Change Log - is a document/tracker of any change that impacted scope, schedule, cost of a project irrespective it is approved, deferred or rejected.

Issue Log - is a document/tracker of a list of issues that surface while testing i.e quality standards of an agreed deliverable or issues from procurement resources.

Both these Logs have details such as Date it is logged, Logged By, Status, Resolution reference if any, attended by, stakeholder details.


Ramakrishna

Few clarifications: issues are not risks but the materialisation of a risk. There is no such thing as 100% likelihood :).
Unlike risks issues have always a negative impact on a project. Issues can be identified in any phase of the project, not only during testing. For example, lack of support from the sponsor is always an issue, although it can be included in the issue register but it must be managed by the project manager.
There are few change registers in a project, each one with his own scope:
1) the change request register, documenting requests to change one of more parameters of the project: scope, budget or time-frame
2) change/decisions log that will contain all the decisions taken to alter the planed activities. For example changing priorities or project resources. Those decisions usually won't trigger a Change Request. The change log is an important instrument in identifying risk and issues as well as supporting change requests. The project change log/register is mainly
3) Technical change log to capture any change done to the production environment. This is managed by the CAB unlike the other 2 that are PMs responsibility