Read the QCST Ticket Timeline

This article explains how the ticket timeline separates the original Description, submitted Ticket Field responses, protected Attachments, public replies, Pro Internal Notes, and system workflow events.

Where this fits in QC Support Ticket

QCST keeps the customer conversation, private staff notes, and system workflow history distinct. Public replies can be shown to the customer; Pro Internal Notes remain staff-only; system timeline entries document events such as assignment, status, relationship, merge, or split operations.

Primary location: QC Support Ticket Agent Queue ticket detail, with global attachment/settings controls under Settings.

How to read the ticket

• Start with the original Description and submitted Ticket Field responses.
• Review Attachments in their protected attachment containers rather than assuming they are message text.
• Read Public replies chronologically for the customer conversation.
• Read Internal Notes separately for staff-only context.
• Use system events to understand assignment/status/command history without confusing them with authored replies.

Important behavior and limits

• Public replies are customer-visible; Pro Internal Notes remain staff-only. System timeline entries record workflow events separately from the conversation.
• Attachments are stored outside normal public delivery and are streamed only after QCST rechecks ticket authorization.

Three kinds of timeline content

Reading order

Use timestamps and entry type together when reconstructing what happened. A system event can explain why the next public reply was routed differently, while an Internal Note can document staff reasoning without exposing it to the requester.

How to reconstruct a case

• Start with the original Description and submitted Ticket Field values to understand the request as received.
• Read public replies in timestamp order to reconstruct the customer-visible conversation.
• Read Internal Notes separately for staff reasoning that was never shown to the requester.
• Use system events to explain routing and workflow transitions such as assignment, Status changes, customer close/reopen or relationship operations.
• Open protected attachments only when needed and authorized; an attachment can be part of the evidence without being part of the message text.

Community Discussion

For practical QC Support Ticket workflows and discussion with other Joomla site owners, visit the QC Support Ticket Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.