TL;DR
Next Tuesday, May 26, we’re folding the dedicated Epics surface into Work Items. Epic becomes a configurable work item type instead of a separate, hardcoded layer. Every epic you have today, with its comments, updates, sub-items, and initiative links, carries over. No data is lost and no workflow breaks. For all Commercial self-hosted users, this will be part of 3.0.0 release.
Why
Treating epics as a separate, hardcoded layer assumed every team works the same way. They do not.. Some teams want a portfolio level above epics, some want a delivery layer below, some do not use epics at all. With Epic as a work item type, your team decides where it sits and what it’s called.
What we’re adding alongside this
We’ve extended Work Item Updates to every work item type, not just epics. Updates continue to roll up to Initiatives the way they do today.
Initiatives accept any work item type, not just epics. You get more freedom in how you structure portfolio-level planning.
What you need to do
For most teams, nothing. We convert your epics in the background, data intact. If you have documentation, saved views, or onboarding material that references epics, that is the one place you should review after the update is rolled out.
Questions
Reply in this thread. We’re tracking this change and answering questions as it rolls out.