An investigation starts with a question or a ticket. Driver gathers evidence, explains the likely cause or answer, and continues with you as you add information.
- Give Driver a starting point. Ask in Investigations, paste a Jira ticket URL, or use the CLI. The early-access investigation MCP App also lets you start from a connected AI tool. Automatic Jira investigations start when a ticket is created in a project where Automatic triage is on.
- Driver reads the available context. It searches connected codebases, documentation, and ticket context. Advanced Codebase Context helps it navigate the prepared system map. Driver suggests likely causes and asks you for the evidence needed to test those explanations and reach a clearer answer. Findings link back to their sources.
- Review the answer. Check the code, commits, or connected sources behind the conclusion. Treat an explanation with missing evidence as a hypothesis to investigate further.
- Continue with more context. Ask a follow-up, identify a relevant version or tenant, or give Driver a log excerpt. Continuing an automated Jira investigation creates your private conversation from its shared starting point.
- Use the result. Prepare a reply, internal note, or engineering handoff from a ticket investigation’s report. Review the wording and evidence, then copy the result to Jira or the tool where the work continues.
- Give feedback. Rate whether the investigation was right, partially right, wrong, or unused, and explain any correction. In Answers, Driver asks whether the response addressed your question.
The automated Jira report is shared through the ticket. Your subsequent conversation with Driver is private. Learn more in Continue a Jira investigation.