Several macros can affect the same ticket draft. A later action can replace an earlier field value, so applying two useful-looking macros does not guarantee the final draft meets the request. Inspect the final status, group, tags and audience before submitting. If a public response contains private investigation detail, fix the draft first. A successful save preserves the final update, not every intermediate field value as a separate ticket state.
Use the named ticket and inspect its stored state after each operation. These tasks move from a guided update to a fresh transfer request. The local model has On-hold enabled and performs no external delivery. A saved field, public comment and follow-up identity each provide different evidence of completion.
Worked example: conflicting macros.