Use case Q06ExecutionEasy

Bug report writer from logs & screenshots

The problem

Bug reports miss steps, environment or evidence, causing 'cannot reproduce' ping-pong.

Workflow

  1. Evidencenotes, logs, screenshot
  2. Vision + LLMreads image and logs
  3. Draftteam bug template
  4. Testerverifies & edits
  5. Jiracreate issue

Real-world example

Tester pastes rough notes, a console log and a screenshot. The AI drafts: title, environment, exact steps, expected vs actual, the key error line ('TypeError: price is undefined at cart.js:212') and a severity suggestion.

Starter prompt

Write a bug report using our template from the notes, log and screenshot. Quote the most relevant
error line exactly. Mark anything you inferred with (assumed). Template: Title, Environment, Steps,
Expected, Actual, Evidence, Severity suggestion.

Tools

Multimodal LLM, Jira via MCP/API

Human check

Mask tokens, passwords and customer data before sending logs to any AI tool.

Measure success

'Cannot reproduce' rate; time to file a bug; reopen rate.

Concepts behind it