Auto-create sprint tickets in Jira from planning docs

PMs spend hours turning planning docs into Jira tickets. An Orkeste agent reads the planning doc, splits it into stories, drafts acceptance criteria, and creates the tickets in Jira after the PM approves each one.

How the workflow runs

1. Ingest planning doc: Reads a Notion or Google Doc planning page, or a Slack thread.
2. Split into stories: Identifies user stories, sub-tasks and dependencies.
3. Draft acceptance criteria: Writes Given/When/Then criteria for each story.
4. PM approves each ticket: PM reviews titles, criteria, estimates and approves in batch.
5. Create in Jira: Tickets are created with the right epic, sprint and assignees.

Human-in-the-loop: No Jira ticket is created without the PM approving the story split and acceptance criteria.

Works with your stack

• jira
• notion
• linear

Related workflows

• Triage incoming bugs in Jira automatically
• Summarize sprint progress in Linear automatically
• Document key decisions in Confluence automatically

Questions about this workflow

Does it estimate story points?

It proposes an estimate based on past similar tickets, the PM has final say.

Can it handle epics and sub-tasks?

Yes. The splitter respects your hierarchy: epic, story, sub-task, with proper linking.

What if scope changes mid-sprint?

Updated planning docs trigger a new diff, and the PM approves added or removed tickets without losing history.