Skip to content

Guides

Hand it to engineering without the bounce-back

An engineering handoff should explain what failed, how to reproduce it, and what evidence supports the suspected cause.

  1. Open the ticket investigation in Driver. If you are reading the automated report linked from Jira, send a message to start your private continuation. Include the latest customer facts, reproduction result, and affected version or branch.
  2. When Driver has finished responding and the ticket report is available, choose Investigation report > Draft > Engineering handoff. Ask for any missing details in the conversation before requesting the draft.
  3. Review the handoff using the checklist below. Correct unsupported claims and limit sensitive customer details to the people who need them.
  4. Use Copy handoff. Paste the reviewed text into the engineering issue in Jira, link the original support ticket, and assign the issue through your normal process.
  5. Add new customer facts to the engineering issue as they arrive. The engineer should start with that issue and the original support ticket, or paste the reviewed handoff into a new Driver investigation.
Include in the handoffEnough detail to continue
Symptom and scopeExpected and observed behavior, tenant, environment, version, and time window.
ReproductionInputs, steps, observed result, and whether your team reproduced the failure.
EvidenceCited codebase, branch, files, relevant ticket comments, and supplied runtime records.
DiagnosisConfirmed finding, competing explanation, and the check needed to distinguish them.
Next stepAttempted workaround, remaining question, and the person who can answer it.

An engineer opening the original automated report starts from the common snapshot. Your later private findings reach them through the handoff you put on Jira. The worked ticket example shows a compact handoff.

When working in Answers, ask Driver for the same handoff structure in the conversation and copy the reviewed response.