Child Tickets

Overview

Child tickets break a large parent ticket (Epic / Story / Initiative) into actionable, independently trackable units. Leera AI automates drafting, linking, refining, and updating these tickets so your team stays focused on delivery instead of admin work.

When to Create Child Tickets

Create them when:

• A parent ticket feels ambiguous or > 1 sprint of effort
• Multiple roles (backend, frontend, QA, DevOps) are involved
• Parallel work streams are possible
• You need clearer burn-down visibility

What Leera AI Can Do

• Propose a work breakdown from a spec or meeting transcript
• Create N scoped child tickets with acceptance criteria
• Link them to the parent automatically
• Enrich titles, descriptions, story points, labels
• Keep status synced (roll-up progress)
• Merge or split existing tickets on request

Quick Start (Fastest Flow)

Say (Slack / Huddle / App): Create 6 child tickets for parent TKT-421 focused on backend API, React UI, and QA automation. Include acceptance criteria and estimate story points.

Common Prompts

Ask Leera:

• Break down parent ticket TKT-421 into backend, UI, and QA tasks. Keep them under 3 points each.
• Add acceptance criteria and test cases to all child tickets under TKT-421.
• Merge child tickets TKT-510 and TKT-511; they are duplicates.
• Split TKT-518 into smaller tasks: keep max 5 hours each.
• Relink orphan child tickets that should belong to TKT-421.
• Summarize progress of all child tickets under TKT-421.

Creating Child Tickets

From a Parent Ticket ID

Create 5 child tickets for TKT-421. Focus on data model, API endpoints, pagination UI, auth edge cases, and regression tests.

From Plain Text

Break this spec into child tickets and suggest parent name:
(paste spec or transcript)

From Meeting / Huddle

After ending a huddle: Summarize action items as child tickets and link to parent Platform Scalability Epic.

Quality Controls

Ask:

• Validate all child tickets under TKT-421 for clarity and missing acceptance criteria.
• Flag any child ticket that lacks test coverage notes.
• Re-estimate child tickets using planning poker ranges (1,2,3,5,8).

Best Practices

• Keep each child ticket: Clear outcome, ≤ 1–2 days effort
• Include: Why, What, Done criteria, Edge cases
• Avoid embedding multiple domains (e.g. backend + QA) in one ticket
• Use consistent labels (e.g. area:api, area:ui, qa)
• Let Leera normalize tense and structure

Structure Template Used by Leera

Title: Actionable outcome
Description:

1. Context
2. Scope
3. Constraints
   Acceptance Criteria:

• Condition / result
• Validation rule Testing:
• Unit
• Integration Estimation: Story points or hours
  Labels: domain, priority, release

Ask: Regenerate child tickets under TKT-421 using the standard template.

Updating & Syncing

Examples:

• Update all child tickets under TKT-421 with current status from commit messages.
• Roll up progress summary for parent.

Cleanup

• Archive completed child tickets older than 30 days.
• List stale child tickets with no activity in 7 days.

Troubleshooting

Issue: Tickets created but not linked
Fix: Relink child tickets created today that mention TKT-421 in description.

Issue: Duplicate scope
Fix: Detect overlapping child tickets under TKT-421 and propose merges.

FAQ

Q: How many child tickets is too many?
A: If coordination overhead > clarity gained or average size < 0.5 points, consolidate.

Q: Can I lock a child ticket from AI edits?
A: Yes: Lock TKT-532 from automated refinement.

Next Steps

• Refine: Improve acceptance criteria for all child tickets under TKT-421.
• Plan: Generate sprint plan based on open child tickets tagged sprint:candidate.
• Track: Daily progress summary at 4 PM.

Sample End-to-End Prompt

From parent TKT-421, generate a balanced set of 7 child tickets (backend, UI, QA). Use standard template, add realistic acceptance criteria, estimate points, and label with area:. Then summarize risk areas.

Need more? Ask: Suggest improvements to current