Back to the Playbook
DefineDE-14
Clean up the backlog
Merge duplicates, close stale items, link every ticket to its epic and intent, and flag work without an owner, so refinement starts from a backlog the team trusts.
Product statusAvailable now
Context in3 required inputsBacklog · Epics and objectives · Related code and components
TransformationProduct Manager + Product AgentAtlassian · Story Discovery · Code Analysis
OutcomeBacklog change proposal: merges, closures, links and flagged tickets.Artifact: Jira story
Owner
Product Manager
Agent-led
Participants · Agents
EngineerProduct Agent
Trigger
A scheduled backlog review, or new tickets arriving without epic, owner or intent.
Required context
JiraBacklogProduct BrainEpics and objectivesCodeRelated code and components
Optional context
Customer evidenceCustomer evidenceJiraEstimatesProduct BrainPrevious decisions
Skills
AtlassianStory DiscoveryCode Analysis
Methods used inside this Activity: Duplicate and relatedness check across tickets and code · Staleness rules by age and activity
Activity steps
- 1Cluster new and old tickets by problem and component.
- 2Propose merges for duplicates and closure for stale items.
- 3Link each ticket to its epic, decision and affected code.
- 4Flag tickets without owner, intent or acceptance criteria.
- 5Apply the approved changes in Jira.
Output
Backlog change proposal: merges, closures, links and flagged tickets.
Artifacts
Updates: Jira story, Epic
What good looks like
- No ticket is closed without a stated reason.
- Merged duplicates keep the evidence of both.
- Every open ticket has an epic and an owner, or a flag.
- Changes stay proposals until approved.
Quality gate
The product manager approves merges and closures before Jira changes.
Destination
JiraTeklens only
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.