Epics is changing in Plane. We're folding the dedicated Epics surface into Work Items, where Epic becomes a configurable work item type alongside the others your team already uses. Your epics, their comments, their updates, and their initiative links all carry over. We delete nothing, and no workflow breaks.

Here is what that means in practice, and why we are making the change

What stays the same

We preserve every epic you have today. The work item itself, its full comment history, its updates, its sub-items, and its connection to any Initiative all remain intact. If your team plans around epics, you can keep planning around epics. The concept is not going anywhere.

What we are changing

We're changing two things. First, we're removing the separate Epics tab from project navigation. Epics will live in the same place as the rest of your work items, filterable and groupable like any other type. Second, Epic stops being a fixed, special-cased entity and becomes a work item type you can enable or disable.

Why we are doing this

Treating epics as a separate, hardcoded layer made an assumption about how every team works, and that assumption did not hold for everyone. Some teams want a portfolio level above epics. Some want a delivery layer below. Some do not use epics at all and want that vocabulary to be something else entirely. When Epic is a work item type rather than a fixed tier, your team decides where it sits and what it is called. The structure follows your process instead of asking your process to follow the structure.

What we're adding alongside this

We're expanding two capabilities so you don't lose anything in the move.

Work Item Updates. The progress updates we previously offered only on epics now work on any work item type. Updates continue to roll up to initiatives the way they do today.

Initiatives accept any work item. We've removed the epics-only limit. You can attach any work item type to an initiative, which gives you more freedom in how you structure portfolio-level planning.

What you need to do

For most use cases, nothing. We convert your epics to the new work item type in the background. Your existing epics move over with all their data intact.

If you have documentation, saved views, or onboarding material that references epics, that is the one place worth a quick review after the update lands.

When this is happening

This ships next week, Tuesday, May 26 for all cloud users. For all Commercial self-hosted users, this will part of 3.0.0. Bring questions to the community forum, where we're tracking this change and answering as it rolls out.