Task Creator

When you open Task Creator, the first screen asks "what do you want to create?" with five options. Hover or focus an option to see an illustrated preview on the right. Click Continue.

Just one task

A single new issue with the right fields. No parent required.

Break a parent into subtasks

Pick one parent issue, then list out N subtasks. Subtasks inherit assignee and priority from the parent by default.

Same task across many parents

Fan-out. Define M task drafts once, pick N parents, Ekko creates M × N issues with the right parent linkage.

Mirror an existing issue

Search a Jira issue, Ekko prefills its fields into a new draft so you can tweak before creating. Great for regressions or recurring chores.

Start from a template

Pick one of your saved templates as the starting point. You can still adjust before creating.

Every flow starts by picking a board. The board determines the project, so Ekko can pre-load issue types, fix versions, sprints, link types, and assignable users.

Every flow renders task drafts as editable cards. Each card has:

• Issue type — driven by the board's configuration.
• Summary — required.
• Description — rich text. Variables work here (see below).
• Priority — every priority configured in your Jira site.
• Assignee — every user assignable on the project.
• Fix versions — every version on the project.
• Sprint — current and future sprints on the board.

You can add and remove drafts freely. Drafts in subtasks/fan-out modes can inherit fields from the parent — toggle "inherit" on a field to lock it to the parent's value.

Drop variables into summaries or descriptions and Ekko replaces them when issues are created. This is the killer feature for templates — same template, different parent, different sprint, different summaries.

{parentSummary}

The summary of the parent issue.

{parentKey}

The parent issue key (e.g. ABC-123).

{parentAssignee}

Display name of the parent's assignee.

{sprintName}

Name of the chosen sprint.

{currentDate}

Today's date in YYYY-MM-DD.

For Subtasks and Fan-out, you pick a parent (or multiple parents). The link type defaults to "is child of" (parent/child) but you can change it to any Jira link type — "blocks", "relates to", "is cloned by", and so on.

A "global parent" option attaches every draft to the same parent in addition to whatever the flow itself sets. Useful when you want all created issues to also hang off an epic.

Each draft can pick a sprint individually, or you can set a "global sprint" that applies to every draft. New issues are created and moved into the chosen sprint in the same flow.

1. 1 The right-hand Live Preview panel shows the exact issue list, with variables expanded against each parent. Counts ("3 parents × 2 drafts = 6 issues") update in real time.
2. 2 Click Create — a confirmation modal expands every draft into its final form so you can review.
3. 3 Confirm. Ekko creates issues in bulk via Jira's bulk-create API, falling back to single-issue create where needed (for example, when setting a non-standard link type).
4. 4 A progress overlay tracks "x of y created" so big batches do not look like they are hanging.
5. 5 On success, a modal lists every created key with one-click Open-in-Jira links.

On the confirmation modal, toggle Save as template and give it a name. Ekko stores the drafts (with their inheritance settings, link types, and variables) so you can recall them in the From Template flow.

Templates are great for:

• Per-story QA tasks (write the template once, fan out every sprint).
• New-hire onboarding checklists.
• Release-cut checklists.
• Recurring chores (security review, dependency upgrades, runbook updates).