When creating an initial support ticket, the primary goal is to provide the support team with a clear and actionable understanding of the problem. A detailed description of the fault (the symptoms) is essential to define what is wrong. Equally important is describing the conditions under which the fault occurs (the context), as this helps in diagnosing the root cause and attempting to replicate the issue. These two pieces of information form the core of the problem statement, which is the necessary first step in any troubleshooting process.

B. Details about the computers connected to the network: This is too broad. Information about all computers is generally unnecessary and clutters the initial report, which should focus on the specific fault.
D. The actions taken to resolve the fault: While this information is very useful to prevent redundant work, it is secondary to first defining the problem itself through a clear description and its context.
E. The description of the top-down fault-finding procedure: This describes a troubleshooting methodology, not specific information about the actual problem being reported in the ticket. ---

1. Cisco Systems

Inc.

"Tips for Opening a Service Request". In its guidance for creating effective support tickets

Cisco explicitly requests a "detailed description of the problem

including the specific symptoms" and information about the context

such as "When did the problem start? What is the frequency of the problem (intermittent or constant)?". This directly supports providing a fault description and the conditions of its occurrence.

Source: Cisco.com

"Tips for Opening a Service Request

" Section: "Information to Have Ready."

2. Cornell University IT Support

"How to Report an IT Problem". University IT departments provide guidance on submitting effective support requests. Cornell's guide advises users to "Describe the problem in detail. What were you trying to do? What happened?" and to specify "When did the problem start?". This emphasizes the importance of describing the fault and the conditions.

Source: Cornell University IT

it.cornell.edu

"How to Report an IT Problem

" Section: "What to Include in Your Report."

3. Carnegie Mellon University

Software Engineering Institute

"A Manager's Guide to Creating a System Trouble-Reporting System

" CMU/SEI-90-TR-021

1991. This technical report on creating trouble-reporting systems outlines the essential fields for a report. Section 3.1

"Problem Report Form

" specifies the need for a "Description of Problem" and "How to Reproduce" the problem

which correspond directly to a detailed fault description and the conditions of occurrence.

Source: Page 10

Section 3.1

"Problem Report Form."