Ticket identity
Start from the source ticket ID and requester context. Similar subjects or organization names do not identify the same request. In a fictional correction, source LC-92 authorizes a type change on ticket 421, while ticket 412 must remain untouched. Read back both records rather than trusting a success notice.
System Priority and a custom field labeled Priority are different. The system field is required for the taught SLA route. Custom fields can represent account-specific data, but their labels do not grant the behavior of built-in fields. Preserve canonical IDs when displaying translated labels.
Solved and Closed
The ticket lifecycle separates Solved from Closed. A requester reply can reopen a solved ticket. A reply to a closed ticket creates a separate follow-up with limited inherited data, not a complete clone of the old conversation and assignment.
Current closed-ticket controls can permit selected metadata corrections. That permission does not reopen the ticket or allow a new comment. Verify the actual account setting, effective actor permission and supported field types before treating a field as editable.
Draft and saved evidence
Changing a field or writing a response in the composer is not the same as Submit. Choose public reply or internal note, submit and inspect the saved event. The Zendesk course practices this with local fictional records, without sending a customer message. Continue with macros and SLA policies to trace later effects.