CAPM Practice: Demonstrate an understanding of common problem-solving tools and techniques

An issue log entry should capture: what the issue is (description), who is responsible for resolving it (owner), how urgent/important it is (priority), when it should be resolved (target resolution date), and where it stands (status). This information ensures issues are tracked, owned, and resolved systematically.

**Why not B:** Change request number, change type, and approval status are elements of a change log or change request form, not an issue log. Issue logs track problems that need resolution, while change logs track proposed modifications to the project.

**Why not C:** Risk probability, risk impact, and risk response strategy are elements of a risk register. The risk register is a separate document from the issue log, tracking uncertain future events rather than current problems requiring resolution.

**Why not D:** Lesson learned, recommendation, and implementation date are elements of a lessons learned register. Lessons learned capture knowledge for future improvement, while issue logs focus on tracking and resolving current project problems.