Back to the Playbook
BuildBU-04
Log bug
Capture a reproducible defect with enough evidence, context and code links for fast triage.
Product statusAvailable now
Context in3 required inputsObserved and expected behaviour · Reproduction steps and environment · Related story or pull request
TransformationQA + QA AgentAtlassian · Code Analysis · Local Files
OutcomeActionable bug report.Artifact: Jira bug
Owner
QA
Human + Agent
Participants · Agents
EngineerQA Agent
Trigger
Observed behaviour differs from expected behaviour.
Required context
FilesObserved and expected behaviourFilesReproduction steps and environmentJiraRelated story or pull request
Optional context
FilesScreenshots and logsCustomer evidenceAffected customerCodeCode analysis
Skills
AtlassianCode AnalysisLocal Files
Activity steps
- 1Confirm the mismatch against the story.
- 2Capture reproduction, scope and severity.
- 3Check for duplicates and link related work and code.
- 4Create the bug.
Output
Actionable bug report.
Artifacts
Creates: Jira bug
What good looks like
- Reproducible where possible.
- Expected versus actual is clear.
- Severity is evidence-based.
- Duplicates are checked.
Quality gate
No human gate before the result is promoted. It stays an Activity result in Teklens until a person decides to use it.
Destination
Jira
Usually next
People and agents work from the same Product Brain. The owner stays accountable. Assigned agents prepare and check. A named person approves at the gate.
Show us exactly how product work happens today.
Thirty minutes with a founder. We compare your process with the Playbook and pick the first Activity to run on your Jira and your repo.