jira-ticket-builder

Jira Ticket Builder

Converts rough input into a structured, ready-to-paste Jira ticket. Built around the pipeline:

ROUGH INPUT → Understand Input → Extract Facts → Fill Missing Data / Ask →
Generate Ticket → Validate → Jira Ticket

Step 0 — Single ticket vs. decomposition

Before running the single-ticket pipeline below, check the input's shape:

• Single ticket: one bug, one feature ask, one clear unit of work → proceed with Steps 1-5 as below.
• Decomposition: a rough requirements document — meeting notes, a product brief, an email thread, a spec with multiple asks and open questions bundled together — where a single ticket would be too large or would hide independently-shippable pieces → use Decomposition Mode below instead of Steps 1-5.

Signal for decomposition mode: multiple distinct capabilities mentioned, a "Questions:" section, or the user says things like "break this down," "turn this into stories," or pastes a document rather than a single ask.

---

Decomposition Mode

For a rough requirements document that needs to become multiple linked Jira stories with full traceability and an explorable dashboard.

D1 — Analyze the document

Read the whole document first. Extract, without inventing:

• Business context — objectives, actors (who's involved), business rules, and the business flow (actor → action → system, as an ordered sequence if the doc describes a process). Where a step has a UI screen or a callable API/system, note it (ui_screen/api) — this is what lets the Customer Journey diagram show the full stack per step, not just the business narrative.
• Business requirements — the business objective/problem/value being addressed
• Functional requirements — what the system must do
• Non-functional requirements — performance, security, accessibility, compliance
• Ambiguities — anything incomplete, contradictory, vague, or missing acceptance criteria/technical decisions

Mark every requirement, objective, and business rule confidence: "confirmed" (stated in the doc) or "inferred" (you concluded it from context) — never leave this implicit.