What other details should be included in the following incident report when it is first submitted?

What other details should be included in the following incident report when it is first submitted?

Date of Issue: 23/11/05

Severity: P1

Build: Version15.6

Details: Expected field to be limited to 15 chars, able to enter 27
A . Suggested solution, priority and number of defects assigned to this developer.
B . Status of the incident, degree of impact, Test Case Number.
C . History, related defects and expected fix time.
D . Line of code, number of defects found, time of day.

View Answer

Answer: B

Explanation:

The other details that should be included in the incident report when it is first submitted are B. Status of the incident, degree of impact, Test Case Number. These details are important to provide information about the current state of the incident, the severity of its effect on the system or user, and the test case that detected the incident. Other details, such as suggested solution, priority, history, related defects, expected fix time, line of code, etc., can be added later during the incident management process. A detailed explanation of incident report can be found in A Study Guide to the ISTQB® Foundation Level 2018 Syllabus, pages 99-1001.