Use Driver to build a timeline between the last successful operation and the first failure, then identify which change could explain the difference.
Prepare the evidence
Provide the Jira ticket URL, tenant, service, environment, and the two timestamps with a timezone. Paste relevant deployment records, configuration changes, and log excerpts, with sensitive details removed. Identify the source and timestamp of each record so Driver can compare events in the correct window.
Ask engineering to map the working and failing versions to accessible codebase branches, or supply the relevant diff. Advanced Codebase Context adds prepared code history for branches whose context is ready.
Compare the changes
- Start a ticket investigation with those inputs. Ask: “Exports last succeeded for Acme at 09:00 UTC and first failed at 10:15 UTC on October 14. Build a timeline from these deployment and error records. Compare the code on the working and failing branches, and separate observed events from possible causes.”
- Ask for one row per event: timestamp, source, change or error, and its connection to the failing path. Have Driver identify any gap in the timeline.
- For each candidate cause, ask which reproduction or log message would confirm or rule it out. Run that check through your support or engineering workflow and give Driver the result.
- Copy the timeline, supported explanation, and remaining question into Jira. For a customer draft, wait for the ticket report, then use Investigation report > Draft > Customer reply and Copy reply. On an automated starting report, send a message first to start your private continuation.
When you only have code evidence, ask which changes could affect the symptom. Keep the deployment and first-failure timing as questions for the service owner until the records are available.