In an IT support scenario, what is a 'ticket' and what should it include?

• A. A ticket is a record of a user issue; should include user details, description, priority, steps to reproduce, and attachments.
• B. A ticket is a financial document for invoicing.
• C. A ticket is a software license key file.
• D. A ticket is a system status dashboard.

Answer: (A)

A ticket is a tracked record of a user-reported IT issue and the work needed to resolve it. This keeps everyone on the same page: who reported the problem, what the issue actually is, how urgent it is, and what steps have been tried. The strongest description of a ticket includes essential details that make troubleshooting possible and the process auditable. A user’s details help you follow up with the right person, a clear description communicates the problem, priority signals how soon it should be addressed, steps to reproduce guide the technician in reproducing the issue, and attachments like screenshots or log files provide concrete evidence to diagnose faster. Additional fields such as environment, category, status, assignee, and a history of updates help manage the lifecycle and ensure service levels are met.

A financial document, a software license key file, or a system status dashboard serve different purposes and don’t function as the structured, actionable record of a single support issue.