Epics
An epic is a task too large for one runner. Jaah never works on it directly: it splits the epic into subtasks and runs them in stages. Analyze pins down the requirements, Design chooses the approach, Plan divides the work into build subtasks, each Coder subtask delivers one merged change, and Finish checks the result as a whole. A stage starts only when the stages before it are done, and each subtask runs like an ordinary task, in its own worktree, with its own state, cost and outcome.
You choose how involved to be when you start it: Unattended lets every stage decide for itself, while Guided has Analyze and Design ask you before they settle the requirements and the design.
An epic has no runner of its own, so its state follows its subtasks: Running while any of them has work to do, Asking while one waits for your answer, Failed when one has used all its attempts, and Done once every subtask is done. A subtask's question goes to the person it or its epic is assigned to, else to whoever created it, as for any task; see Answer a task's question.
An epic is not a feature. A feature only groups related tasks inside a project and never runs anything; an epic can sit in a feature like any other task. The ideas behind both are in How epics and features work.
- How epics and features work — when to choose an epic, what each stage hands on, involvement, and how the epic's state follows its subtasks.
- Start an epic and follow its stages — start the epic from the board, then watch Prepare, the build phases and Finish, and read the result.
- See which stage a running epic is on — its progress ring on the board, and the subtask running now or what it waits on under Runner.
- Turn a draft into an epic — change a saved draft's size to Epic, then save it or start it.
- Turn an epic back into a single task — change an epic's size to Task, so one runner does the work and its subtasks are archived.
- Review an epic's requirements, design and plan — read what Analyze, Design and Plan decided, and the answers they were given.
- Answer the questions a guided epic asks — find the subtask waiting for you, answer it on its Q&A tab, and let the epic carry on.
- Steer an epic's subtasks — start a subtask early, or stop or redo one.
- Run an epic again from the start — reset the epic and all its subtasks, change its brief, and start it from Analyze.
- Get a failed epic going again — find the subtask that failed, fix it and start it, so the epic carries on.
- Run an epic one stage at a time — set Throttle to Manual so each subtask waits, read each stage, then start the next.
- Limit how many subtasks run at once — set Throttle to a number when you start an epic, or change it while it runs.
- Pause an epic and pick it up later — stop the epic and its running subtasks, keep their work, and start it again later.
- Hide an epic and its subtasks from the board — tick Hidden on the epic so it and its subtasks leave the board, find it with the Hidden filter, and show it again.
- Hand an epic to a teammate — change the epic's Assigned to so its subtasks' questions reach them, or reassign one subtask.
- Give a feature an owner and a progress ring — mark a feature with an icon, name who leads it, and show how much of it is done.
- Hand a feature to a new owner — pick a feature's new owner on its page when the person leading it moves on.
- Arrange features in the sidebar — add a feature from the sidebar, order and pin features, and drag tasks onto them.
- Close a finished feature — check its tasks are done, move out the rest, and delete it.
- File an epic under a feature — pick a feature in the epic's breadcrumb; its subtasks, and any added later, follow it.
- File a task under a new feature — create a feature from a task's breadcrumb and return with the task filed under it.
- Rename a feature — change a feature's name or the description shown above its tasks.
- Find a feature in the sidebar — type part of its name in Find a project or feature and open its tasks.
- Hide a feature you don't work on — take it out of your sidebar and its tasks off your board, for you only, and show it again.
- Check what a finished epic delivered — read its Finisher notes, its pull requests and follow-ups, and fix what is unresolved.
- Group the board by feature — show one section per feature, with each project's tasks outside any feature after them.
- Change an epic's priority — raise or lower an epic so every unfinished subtask takes the new level.
- See what an epic cost — read the whole epic's cost on its Metrics tab, then each subtask's share.
- Make an epic wait for another task — add a prerequisite in Depends on so none of the epic's stages starts until it is done.
- Start an epic on a schedule: have an automation file the same epic on a timer, with its involvement, Throttle and assignee set once.
Grouping tasks is covered in Organize tasks into features, and the Subtasks tab is described in Task page.