Teklens logo
DEEN
Back to the Playbook
BuildQualityBU-05

Triage bug

Decide severity, priority, owner and next action for a defect, with the likely cause already located in the code and a fix proposal prepared.

Product statusAvailable nowTriage and fix proposal are available. Handing the fix to a coding agent is in beta; Teklens Agents do not write code themselves.

Context in4 required inputsBug report · Affected users and impact · Related code and change history
TransformationEngineer + Engineering Agent + QA AgentAtlassian · Code Analysis · Find Code Owners
OutcomeTriaged bug with rationale, owner and fix proposal.Artifact: Jira bug

Why it matters

Bug triage without senior capacity: the agent finds the likely cause in the code and previous fixes, clusters similar reports, and prepares the fix. A person decides priority and owner.

Owner

Engineer

Human + Agent

Participants · Agents

Product ManagerEngineering AgentQA Agent

Trigger

Event-drivenA new bug, a spike of similar reports, or a material change in an existing bug.

Required context

JiraBug reportCustomer evidenceAffected users and impactCodeRelated code and change historyProduct BrainCurrent priorities

Optional context

CodePrevious fixesFilesWorkaroundFilesSLA or revenue impactJiraDuplicate bugs

Skills

AtlassianCode AnalysisFind Code Owners

Methods used inside this Activity: Severity and priority separated · Bug clustering by symptom and component

Activity steps

  1. 1Validate the bug and find duplicates and clusters.
  2. 2Locate the likely cause in the code and previous fixes.
  3. 3Identify the owner and assess the impact.
  4. 4Set severity and priority and decide fix, defer or close.
  5. 5Prepare the fix proposal for the engineer or coding agent.

Output

Triaged bug with rationale, owner and fix proposal.

Artifacts

Updates: Jira bug

What good looks like

  • Severity and priority are separated.
  • Customer and business impact is explicit.
  • The likely cause is linked to code.
  • Owner and next action are clear.

Quality gate

Product or engineering approves critical priority changes.

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.

Deep dives from the AI PM Lab

Articles that explain the thinking behind this Activity.

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.

Book a demoBack to the Playbook