Skip to content
Astera Technology

Separate requested outcomes inside one support ticket

Track a failed task and a separate customer question without letting one answer close both.

Identify what would satisfy each request

Synthetic ticket T-11 reports that a monthly export omits row R-8 and also asks how to change the report title. These are two requested outcomes in one conversation. The fixture closes the parent only when both outcomes have a recorded disposition. Explaining the title setting resolves the question but supplies no evidence that the missing row was restored. Keep both linked to the same customer report.

Filled synthetic support record
OutcomeEvidenceCurrent stateNext action
O-ROWR-8 absent in supplied exportInvestigatingCompare output with agreed row set
O-TITLECustomer confirms title instructions workAnsweredRetain confirmation
T-11 parentOne outcome still openOpenContinue missing-row task
Download editable CSV ↓

Close outcomes before the parent

  1. List requested outcomes
  2. Create linked outcome records
  3. Record each answer or repair
  4. Close parent after every disposition

A new question in a later reply is recorded explicitly; do not overwrite the original failure to make the ticket look resolved.

How many outcomes remain open after the title answer?

Show the worked answer

One, O-ROW. O-TITLE is answered; the parent stays open until the missing-row outcome is resolved or otherwise explicitly disposed.

Agree the disposition for every requested outcome. New questions can join the conversation without erasing the original unresolved work.

Related resources

Custom software development →