> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bluegenai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Epics

> Epics group Tickets and set the order work gets built in, and how re-evaluating them affects manual changes.

<Frame caption="The Epics view. Each row shows a stable id, the name, progress, and the wave badge marking its position.">
  <img src="https://mintcdn.com/bluegenai/NDGsqiI6WIlzZ3zL/images/tickets/epics-list.png?fit=max&auto=format&n=NDGsqiI6WIlzZ3zL&q=85&s=00f76bfbbe9fdf20029242934d897071" alt="The Epics view listing nine epics from EPIC-001 Authentication and Session Management through EPIC-009 User Preferences and Accessibility, each with a progress readout, a blue wave badge, and edit and delete icons, followed by an Unassigned row." width="1512" height="788" data-path="images/tickets/epics-list.png" />
</Frame>

## Epics and Waves

**Epics are groups of Tickets while Waves are the order of work.**

An Epic is the group. Its position in the build order is its Wave. The first Epic to be worked is Wave 1.

By default, Epics and Waves will have the same number. Epic 1 will be Wave 1. However user's have the ability to manually re-order Epics to perform the work as desired. When an Epic is moved to a different order, the Wave it corresponds to will be moved.

If Epic 3 is moved to the top, it will become Wave 1 while still being named Epic 3.

The Tickets list and the detail panel show **Epic** and **Wave** as separate fields, which makes them look like two things you set. You only ever set one. Move an Epic up or down and its Wave follows automatically; reorder the list and every Wave renumbers to match.

There is no way to manually give a Ticket a Wave without putting it in an Epic.

<Note>
  If you are reading a Ticket and wondering which field to change, the answer is neither. Wave is a readout of where its Epic sits. Move the Ticket to a different Epic, or move the Epic itself.
</Note>

## Reading an Epic Row

| Element     | What it tells you                         |
| ----------- | ----------------------------------------- |
| `EPIC-001`  | A stable id that survives reordering      |
| Name        | What the group covers, at a high level    |
| `5/5 done`  | Closed Tickets against total in that Epic |
| `Wave 1`    | Its position in the build order           |
| Drag handle | Reorder by dragging                       |

At the bottom sits an **Unassigned** row holding Tickets that belong to no Epic. It has no id, no wave badge, and no edit or delete controls, because it is a bucket rather than an Epic. The count in the header excludes it.

## Working with Epics

<Frame caption="An expanded Epic. The overflow control on each Ticket row opens a searchable picker for moving it to another Epic.">
  <img src="https://mintcdn.com/bluegenai/NDGsqiI6WIlzZ3zL/images/tickets/epics-expanded.png?fit=max&auto=format&n=NDGsqiI6WIlzZ3zL&q=85&s=9bcca627a153c8fea7027e0b897d4dfd" alt="An expanded epic showing its child ticket rows, each with a drag handle, ticket id, title, an inline status dropdown, an assignee dash, and an overflow button." width="1512" height="788" data-path="images/tickets/epics-expanded.png" />
</Frame>

**New Epic** adds one at the end of the list. It is an inline field rather than a dialog, and the add control stays disabled until you type a name.

**Reordering** works by dragging, either an Epic among Epics or a Ticket within an Epic. Re-ordering an Epic changes its Wave #.<br />Moving a Ticket between Epics is done through the overflow control on its row, which opens a searchable list of every Epic.

**Deleting** an Epic does not delete its Tickets. They fall back to **Unassigned** and the remaining Waves renumber.

## Re-evaluate Build Order

**This is the most destructive control in Tickets.** It deletes every Epic and rebuilds the whole grouping from scratch using AI. Use only when you are confident a comprehensive re-work is warranted.

<Frame caption="The Re-evaluate confirmation names exactly what is lost.">
  <img src="https://mintcdn.com/bluegenai/NDGsqiI6WIlzZ3zL/images/tickets/epics-re-evaluate-warning.png?fit=max&auto=format&n=NDGsqiI6WIlzZ3zL&q=85&s=1096c5a48befee385fb58ba2507a5a19" alt="The Re-evaluate Build Order confirmation dialog warning that all existing epics will be deleted and re-created from scratch, that manual changes including renames, custom epics and ticket assignments will be lost, and that the action cannot be undone." width="1512" height="788" data-path="images/tickets/epics-re-evaluate-warning.png" />
</Frame>

What gets deleted: every Epic you renamed, every Epic you created by hand, and every Ticket assignment you made. What survives: the Tickets themselves, which are regrouped rather than deleted.

<Warning>
  Re-evaluating discards manual grouping work with no way back. Use it when the grouping is wrong enough to be worth restarting, not to refresh a mostly-good build order.
</Warning>

## Your Next Step

With work grouped and ordered, a Ticket can be handed to the build agent.

<CardGroup cols={2}>
  <Card title="Build from a Ticket" icon="code" href="/tickets/using-tickets-in-build-mode">
    Referencing a Ticket in a Build conversation, and what context comes with it.
  </Card>

  <Card title="Adjust individual Tickets" icon="pen-line" href="/tickets/creating-editing-tickets">
    Editing, reassigning, and deleting Tickets by hand.
  </Card>
</CardGroup>


## Related topics

- [Using Tickets and Epics in Build Mode](/tickets/using-tickets-in-build-mode.md)
- [What are Tickets and how do they help me?](/tickets/what-are-tickets.md)
- [Troubleshooting & FAQ](/tips-and-tricks/troubleshooting-faq.md)
- [Cloning your project](/admin-platform/cloning-your-project.md)
- [CAB-to-Ticket conversion](/tickets/cab-to-ticket-conversion.md)