diff --git a/docs/ai/pi-chat.md b/docs/ai/pi-chat.md
index c2dd9e6..e991b2c 100644
--- a/docs/ai/pi-chat.md
+++ b/docs/ai/pi-chat.md
@@ -179,7 +179,7 @@ Manage your projects:
- Create new projects with descriptions.
- Update project details (name, description, identifier, cover image).
- Delete projects.
-- Enable or disable project features (Epics, Cycles, Modules, Pages, Views).
+- Enable or disable project features (Cycles, Modules, Pages, Views).
_Example commands:_
@@ -299,7 +299,7 @@ Align work with strategic goals:
- Create, update, or delete initiative-specific labels.
- Attach or remove labels from initiatives.
- Link or unlink projects to initiatives.
-- Link or unlink epics to initiatives.
+- Link or unlink work items to initiatives.
_Example commands:_
diff --git a/docs/communication-and-collaboration/notifications.md b/docs/communication-and-collaboration/notifications.md
index 771376e..bf7f67d 100644
--- a/docs/communication-and-collaboration/notifications.md
+++ b/docs/communication-and-collaboration/notifications.md
@@ -39,8 +39,7 @@ Inbox notifications always come through regardless of these settings. These togg
| Work item relation added or removed (blocked by, duplicate, etc.) | Yes |
| Work item deleted | Yes |
| @mention in description or comment | Yes (mention notification) |
-| Epic field updated | Yes |
-| Epic update published (progress or status post) | Yes — all epic subscribers get an email |
+| Work item update published (progress or status post) | Yes — all work item subscribers get an email |
| Due date approaching (reminder) | Yes — subscribers and assignees get an in-app and email notification |
## Notification channels
diff --git a/docs/communication-and-collaboration/subscribers.md b/docs/communication-and-collaboration/subscribers.md
index 5001f09..5558cc7 100644
--- a/docs/communication-and-collaboration/subscribers.md
+++ b/docs/communication-and-collaboration/subscribers.md
@@ -1,11 +1,11 @@
---
title: Subscribers
-description: Learn how to subscribe to work items and epics in Plane, manage subscriber lists, set up project-level auto-subscriptions, and understand how Plane subscribes you automatically.
+description: Learn how to subscribe to work items in Plane, manage subscriber lists, set up project-level auto-subscriptions, and understand how Plane subscribes you automatically.
---
# Subscribers
-A subscription is how you tell Plane to keep you in the loop on a work item or epic. When you're subscribed, you get notified whenever something changes — a state update, a new comment, a priority shift, an assignee change.
+A subscription is how you tell Plane to keep you in the loop on a work item. When you're subscribed, you get notified whenever something changes — a state update, a new comment, a priority shift, an assignee change.
You don't always have to subscribe manually. Plane adds you automatically in a few situations: when you're assigned to something, when someone @-mentions you, or when an admin has set you up as a project-level subscriber. Everything else is opt-in.
@@ -21,18 +21,6 @@ Open the work item and click **Unsubscribe**. That's it — you'll stop receivin
If you were auto-subscribed (because you were assigned, for example), unsubscribing works the same way. Being removed as an assignee doesn't automatically unsubscribe you — you have to do that yourself if you want to stop getting notifications.
-## Subscribe to an epic
-
-Epics have their own subscribe flow, separate from work items.
-
-Open an epic and click the **Subscribe** button in the detail panel. You'll get notified when the epic itself changes — field updates, state changes, comments, and when an epic update (a progress or status post) is published.
-
-Epics work the same way as work items for most notifications. The one thing that's different is **epic updates**. When someone publishes a progress or status update on an epic, Plane sends an email specifically to all epic subscribers. This is separate from the usual change notifications — it's more like a broadcast, letting stakeholders know about deliberate progress posts rather than individual field edits.
-
-If you're subscribed to an epic, you get both: notifications for changes to the epic itself, and emails when an epic update is published.
-
-To unsubscribe, click **Unsubscribe** from the same panel.
-
## Subscribe to multiple work items at once
If you need to subscribe to several work items in one go:
diff --git a/docs/core-concepts/analytics.md b/docs/core-concepts/analytics.md
index ff0a1f0..ef92b3b 100644
--- a/docs/core-concepts/analytics.md
+++ b/docs/core-concepts/analytics.md
@@ -40,7 +40,7 @@ The Projects analytics tab gives you a clear snapshot of how all your projects a
The _Projects by status_ chart breaks things down by where each project sits in its lifecycle. You can see how many projects are still in draft phase versus those that are actively in execution. It's a handy way to understand your project pipeline and see if you've got a good balance between planning and doing.
-Below that, you'll find a detailed table that shows you the nitty-gritty details - how many team members are involved, the number of epics and work items, which cycles and modules are part of the project, and even how many pages and views have been created. There's also an intake column that tracks incoming requests or ideas for each project.
+Below that, you'll find a detailed table that shows you the nitty-gritty details - how many team members are involved, the number of work items, which cycles and modules are part of the project, and even how many pages and views have been created. There's also an intake column that tracks incoming requests or ideas for each project.
What's really useful here is that you can search through all your projects if you're looking for something specific, and of course, export everything to CSV if you want to do some deeper analysis or create reports for stakeholders.
diff --git a/docs/core-concepts/issues/display-options.md b/docs/core-concepts/issues/display-options.md
index 56e722f..94e071f 100644
--- a/docs/core-concepts/issues/display-options.md
+++ b/docs/core-concepts/issues/display-options.md
@@ -42,7 +42,6 @@ Grouping helps you organize work items based on shared attributes, making it eas
- Assignees
- Created By
- Milestones
-- Epics
- Releases
- Work Item Types
- None
@@ -59,7 +58,6 @@ You can further refine your view by adding a sub-grouping. For example, you coul
- Assignees
- Created By
- Milestones
-- Epics
- Releases
- Work Item Types
- None
diff --git a/docs/core-concepts/issues/epics.md b/docs/core-concepts/issues/epics.md
index 988df8e..6e41141 100644
--- a/docs/core-concepts/issues/epics.md
+++ b/docs/core-concepts/issues/epics.md
@@ -1,171 +1,37 @@
---
-title: Organize related work items with Epics
-description: Create and manage Epics in Plane to organize related work items, track progress across multiple tasks, and align your team around larger objectives.
+title: Epics
+description: Epics are now a work item type in Plane. Learn what changed, what stayed the same, and where to go next.
---
# Epics
-Epics help you group related tasks into a larger work item, providing a hierarchical structure for managing complex projects. This feature is ideal for breaking down major objectives into smaller, manageable pieces while keeping everything organized within a project.
+Epics in Plane have moved. They're now a [**work item type**](/work-items/project-work-item-types), living in the same Work Items list as other types your team tracks. If you've been using Epics, this page explains what changed, what stayed the same, and where everything is now.
-Use Epics when you need to:
+## What changed
-- Organize tasks related to a larger objective or feature.
-- Track progress and dependencies across multiple related work items.
-- Improve visibility into how individual tasks contribute to broader goals.
+Previously, Epics had their own dedicated tab in the project sidebar. You managed them separately from work items, and they had their own filtered view, their own settings toggle, and their own sidebar entry.
-::: tip
-Use an Epic for larger bodies of work that span multiple cycles and extend across different modules.
-:::
+That separate layer is gone.
-## Turn on Epics
+Epic is now a **work item type** and is treated exactly like any other type. You filter, group, sort, and manage Epics the same way you work with any other work item. The creation form, the detail view, the bulk editor, the filters, all of it is shared.
-
+What this means in practice:
-To start using Epics, turn on the feature for your project:
+- **The Epics tab in the sidebar is removed.** Epics live in **Work Items**, filterable by type.
+- **The Epics toggle in Project Settings is gone.** Epic is now managed under **Work item Types** settings. If Work Item Types are enabled for your project, Epic is there.
+- **Epic is created automatically.** When you enable Work Item Types for a project, Plane creates two types: the default **Task** type and an **Epic** type. You don't set them up manually.
+- **Work Item Updates - On Track, At Risk, Off Track - are no longer exclusive to epics.** They're now available on every work item of every type.
-1. Go to the [Project settings](/core-concepts/projects/overview#configure-project-settings) for the desired project.
-2. Navigate to the **Epics** section on the right pane.
-3. Click the **Enable** button.
+The levels aren't arbitrary. Task is created at level 0 and Epic at level 1 - this is the default hierarchy structure built into the product. If your workspace has the Hierarchy feature enabled, that structure is enforced automatically: Epics sit above Tasks, Tasks can be sub-items of Epics, and Tasks cannot contain Epics. You don't configure this; it's there by default the moment Work Item Types are enabled.
-Once turned on, the Epics tab will appear in the project's sidebar, giving you quick access to create and manage Epics.
+## What stayed the same
-## Add custom properties to Epics
+The data is fully intact. Every comment, every activity log entry, every update, every sub-work item relationship, and every initiative link on your existing epics carried over. Nothing was lost.
-Custom properties allow you to add specialized fields to your Epics, helping you track additional information specific to your project's needs. These properties can be configured to capture various types of data.
+The way Epics work conceptually hasn't changed either. An epic is still the parent layer above individual work items. Work items still link to an epic through the **Parent** field. Updates from epics still feed into initiative streams as for all work items.
-
+## Where to find your epics now
-To add custom properties to an Epic:
+Open **Work Items** in your project. Click **Filters**, add a **Type** filter, and select **Epic**. Your epics are there, exactly as you left them.
-1. Click the **Add new property** button on the Epics pane.
-2. In the **Custom Properties** section, fill in the following fields:
- - **Title**: Enter a name for your property
- - **Description**: Add details about what this property represents
- - **Property type**: Select from the available options:
- - **Text**: For free-form text input
- - **Number**: For numerical values
- - **Dropdown**: For predefined selection options
- - **Boolean**: For yes/no or true/false values
- - **Date**: For temporal information
- - **Member picker**: For assigning team members
-
-## Create Epics
-
-
-
-Follow these steps to create a new Epic:
-
-1. Navigate to the **Epics** section under your project.
-2. Click the **New Epic** button at the top right of the screen.
-3. Provide the following details:
- - **Title**: Name your Epic.
- - **Description**: Add context for the Epic’s purpose.
- - **Properties**: Assign metadata like priority, assignees, labels, and due dates.
-4. Click **Save** to create the Epic.
-
-## View and manage Epics
-
-Once created, all Epics can be accessed from the **Epics** section under your project. The Epics screen provides a high-level view of all Epics within a project.
-
-
-
-::: tip Sort and filter Epics
-To help you manage Epics effectively, Plane offers flexible sorting and filtering options.
-:::
-
-Clicking on an Epic opens a detailed view where you can quickly view and manage an Epic without leaving your current context.
-
-## Add work items to Epic
-
-
-
-You can add existing work items to the Epic or create new ones directly from the Epic.
-
-::: warning important
-A work item can belong to only one Epic. This ensures clarity in organization and avoids overlapping tasks across multiple Epics.
-:::
-
-## Duplicate Epics
-
-When you need to create similar Epics or replicate an Epic's structure across projects, Plane allows you to duplicate existing Epics either within the same project or to different projects in your workspace.
-
-To duplicate an Epic, click the ••• menu in the Epic header and select Make a copy. You'll see two options:
-
-### Copy in same project
-
-Creates an identical Epic within the current project with all the same properties, description, and custom field values. The new Epic gets a fresh identifier and maintains the same title, description state, priority, start and due dates.
-
-### Copy in different project
-
-Duplicates the Epic to another project in your workspace that has Epics enabled. This is particularly useful when you have similar large-scale objectives across multiple projects or want to replicate Epics between projects. The copied Epic adapts to the destination project's identifier format and default state.
-
-## Work items list and relations
-
-
-
-- See the full list of work items grouped under the Epic.
-- Add or remove work items from the Epic.
-- Manage work items directly by updating their status, assignee, or priority.
-
-## Epic progress
-
-
-
-You can track Epic progress visually with a color-coded progress bar that shows:
-
-- Task completion status (e.g., Backlog, Started, Completed).
-- Work item counts and completion percentage for each status category.
-
-## Epic updates
-
-Share epic status using updates. This helps keep your team informed and create a timeline of epic progress.
-
-1. Select the tab with rocket icon in the side panel.
-2. Click the **Add Update** button.
-3. Select the status. Each update can be marked as:
- - 🚀 **On Track** - Epic is progressing as planned
- - ⚠️ **At Risk** - There are potential work items that need attention
- - ❗ **Off Track** - Epic has significant blockers or delays
-4. Add your update message.
-5. Click **Add update**.
-
-
-
-### Collaborate on updates
-
-- Start threaded discussions around specific updates or tasks.
-- Use emoji reactions for quick feedback.
-
-## Properties, comments, and activity
-
-- View and update the Epic’s key properties like assignee, priority, timelines, and other custom properties.
-
- 
-
-- Add comments to collaborate with your team and to discuss progress, blockers, or updates.
-
- 
-
-- Access the activity log for a history of changes made to the Epic, ensuring transparency and accountability.
-
- 
-
-## Link Work items to Epics
-
-For each work item, you can assign or change a work item's Epic directly in the **Parent** property.
-
-
-
-## Convert Epics to Work Items
-
-Sometimes you realize that what you thought was a big, complex epic is actually something smaller and more focused. That's where converting an epic to a work item comes in handy. This feature lets you transform an epic into a regular work item, making it easier to track and manage as a single deliverable rather than a collection of tasks.
-
-
-
-From any epic, look for the conversion option in the interface. Click **Convert to work item** and the system will transform your epic while preserving all the important details like title, description, and basic properties.
-
-You can also [convert Work items to Epics](/core-concepts/issues/overview#convert-work-items-to-epics).
-
----
-
-Epics provide a simple yet powerful way to manage larger goals while keeping your projects organized and your team aligned.
+You can also group your Work Items view by **Type** to see epics and other types side by side.
diff --git a/docs/core-concepts/issues/overview.md b/docs/core-concepts/issues/overview.md
index 8a00455..643568a 100644
--- a/docs/core-concepts/issues/overview.md
+++ b/docs/core-concepts/issues/overview.md
@@ -193,15 +193,29 @@ Connect relevant project pages and wiki documentation to your work items to prov
Linked pages appear directly in the work item, making it easy for team members to access relevant documentation without leaving the context of their current task.
-## Convert work items to epics
+## Work item updates
-Sometimes a work item grows in scope and complexity, and you realize it's actually big enough to be its own epic with multiple sub-tasks. This feature promotes a regular work item into an epic, giving you the structure and flexibility to break it down into smaller, manageable pieces.
+Updates let you post a status snapshot on any work item. Each update carries a status indicator — On Track, At Risk, or Off Track — alongside a message.
-
+**Post an update:**
-From any work item, find the **Convert to Epic** option. The system will ask you to confirm since this action detaches any associated cycles, modules, and parent items. Once converted, you'll have a new epic that you can start breaking down into sub-work items and organizing however makes sense for your project.
+1. Open the work item.
+2. Click the **Updates** tab in the side panel.
+3. Click **Add Update**.
+4. Select a status:
+ - **On Track** — progressing as planned
+ - **At Risk** — potential blockers that need attention
+ - **Off Track** — significant blockers or delays
+5. Add your message.
+6. Click **Add update**.
-You can also [convert Epics to Work Items](/core-concepts/issues/epics#convert-epics-to-work-items).
+Updates roll up to any initiative the work item is linked to.
+
+## Change a work item's type
+
+To change a work item to an Epic or any other type - use **Switch work item type**. Open the work item, hover next to the work item ID, and click **Switch work item type**. Select the new type from the dropdown and click **Update**.
+
+See [Work Item Types](/work-items/project-work-item-types#switch-work-item-types) for full details.
## Activity and collaboration
diff --git a/docs/core-concepts/projects/initiatives.md b/docs/core-concepts/projects/initiatives.md
index a642eba..dfa9c17 100644
--- a/docs/core-concepts/projects/initiatives.md
+++ b/docs/core-concepts/projects/initiatives.md
@@ -1,11 +1,11 @@
---
title: Align multiple projects with Initiatives
-description: Create and manage Initiatives to align multiple projects with strategic goals, track cross-project epics, and monitor aggregated progress.
+description: Create and manage Initiatives to align multiple projects with strategic goals, track cross-project work items, and monitor aggregated progress.
---
# Initiatives
-Initiatives is designed to help you manage and track progress across multiple related projects under a unified objective. This feature is particularly useful if you need a high-level view of how various projects align with strategic goals.
+Initiatives helps you manage and track progress across multiple related projects under a unified objective. Use it when you need a high-level view of how various projects and work items align with strategic goals.
Use Initiatives when you need to:
@@ -13,7 +13,7 @@ Use Initiatives when you need to:
- Manage and monitor groups of related projects efficiently.
- Provide stakeholders with an aggregated view of progress and status.
-## Enable Initiatives
+## Activate Initiatives
To start using Initiatives, you'll need to enable the feature:
@@ -25,7 +25,7 @@ To start using Initiatives, you'll need to enable the feature:
Once enabled, you'll see an **Initiatives** option in the sidebar under **Workspace** section.
-## Create initiatives
+## Create an initiative

@@ -62,7 +62,7 @@ Initiatives offers three distinct layouts to help you visualize and manage your
#### List layout
-The default view that displays Initiatives in a structured list format, showing key details like progress status, dates, connected projects and epics, leads, and states at a glance. This layout is ideal for quickly scanning through multiple Initiatives and comparing their high-level status.
+The default view that displays Initiatives in a structured list format, showing key details like progress status, dates, connected projects and work items, leads, and states at a glance. This layout is ideal for quickly scanning through multiple Initiatives and comparing their high-level status.
#### Board layout
@@ -76,7 +76,7 @@ All three layouts support filtering and grouping in the top navigation.
### Initiative overview
-The **Overview** gives you a bird's-eye view of your Initiative's progress. You'll see a comprehensive scope breakdown that tracks both projects and epics within your initiative, showing completion percentages and recent updates at a glance.
+The **Overview** gives you a bird's-eye view of your Initiative's progress. You'll see a comprehensive scope breakdown that tracks both projects and work items within your initiative, showing completion percentages and recent updates at a glance.
The progress visualization at the bottom provides an instant snapshot of work distribution across different states - from backlog items to completed work. The percentages and counts for each category are automatically calculated based on the associated projects. This makes it easy to understand where your initiative stands and identify any bottlenecks in your workflow.
@@ -90,25 +90,21 @@ Use Initiatives for a top-down view of progress. For detailed updates, navigate
Use the dropdown in the top navigation to switch to the **Scope** view to see all the building blocks of your initiative. Here you'll find detailed lists of:
-**Epics**
-With Initiatives, you can bring together Epics from different projects into a single, high-level view. This helps you track progress across multiple workstreams in one place, giving you a clear picture of how everything is moving forward.
+**Work items**
+You can bring together work items from different projects into a single, high-level view under one initiative. This gives you a centralized picture of how everything is moving forward across workstreams.
-Here’s how it helps:
+Any work item type can be added to an initiative — Tasks, Bugs, Features, Epics, or any custom type your workspace uses. You are not limited to a single type.
-- Group related Epics from different projects under one Initiative to keep everything connected.
-- Get a centralized view of progress, dependencies, and blockers across multiple projects.
-- No more jumping between projects—track and manage Epics in one place.
+Adding work items to an initiative lets you:
-After you create an Initiative and add Epics from any project. From there, you can monitor overall progress, update statuses, and ensure everything stays on track.
-
-This is perfect for cross-functional teams working on company-wide objectives, product launches, or any effort that spans multiple projects.
+- Group related work from different projects under one goal.
+- Track progress, dependencies, and blockers across multiple projects in one place.
+- Monitor overall progress and update statuses without switching between projects.
**Projects**
-Connected projects showing completion rates and key details like execution status, leads, and timelines.
-
-Each item shows its current progress, making it simple to drill down into specific areas that need attention or are ready for the next phase.
+Connected projects showing completion rates and key details like execution status, leads, and timelines. Each item shows its current progress, making it simple to drill down into specific areas that need attention or are ready for the next phase.
-Use the **Add scope** button in the top-right corner to expand your initiative by connecting additional epics and projects. This makes it easy to grow your initiative as new work streams emerge or when you need to link existing work to your strategic goals.
+Use the **Add scope** button in the top-right corner to expand your initiative by connecting additional work items and projects. This makes it easy to grow your initiative as new work streams emerge or when you need to link existing work to your strategic goals.
### Initiative states
@@ -143,10 +139,10 @@ Once labels are created, you can assign them to any Initiative through the **Lab

-The Initiative updates stream displays all project and epic updates in a chronological feed at the top of the Initiative view. Each update card shows:
+The Initiative updates stream displays all project and work item updates in a chronological feed at the top of the Initiative view. Each update card shows:
- Status indicators (On Track, At Risk, Off Track)
-- Source project or epic name
+- Source project or work item name
- Post date and author
- Complete update content
@@ -157,7 +153,7 @@ This consolidated view enables Initiative owners to monitor progress across all
- The Info tab on the side panel of an Initiative provides a quick snapshot of key properties and metadata associated with the Initiative.
- **State**: Track the Initiative's lifecycle phase (Drafts, Planned, Active, Completed, Closed)
- **Projects**: Number of connected projects
- - **Epics**: Number of associated epics
+ - **Work items**: Number of associated work items
- **Lead**: Person responsible for the Initiative
- **Start date**: When the Initiative begins
- **Due date**: Target completion date
diff --git a/docs/core-concepts/projects/manage-project-members.md b/docs/core-concepts/projects/manage-project-members.md
index 7b83916..72fa051 100644
--- a/docs/core-concepts/projects/manage-project-members.md
+++ b/docs/core-concepts/projects/manage-project-members.md
@@ -39,7 +39,7 @@ The member now has access to the project with the permissions defined by their r
### Project roles
- **Admin** — Full project access including settings, member management, and all features.
-- **Contributor** — Can create and manage work items, epics, cycles, modules, pages, and views. Can delete content they created themselves.
+- **Contributor** — Can create and manage work items, cycles, modules, pages, and views. Can delete content they created themselves.
- **Commenter** — Can view all work items in the project and add comments and reactions. Can also create intake submissions.
- **Guest** — Limited access. Can submit intake forms and view, edit, and delete intake issues they created.
diff --git a/docs/core-concepts/projects/milestones.md b/docs/core-concepts/projects/milestones.md
index 48a2b32..07314db 100644
--- a/docs/core-concepts/projects/milestones.md
+++ b/docs/core-concepts/projects/milestones.md
@@ -5,7 +5,7 @@ description: Align work items toward shared completion dates with milestones. Tr
# Milestones
-Milestones provide a layer to align work items and epics toward shared completion dates, helping teams focus on strategic objectives and critical deliverables. Whether tracking quarterly goals, product launches, or major feature releases, milestones give you visibility into progress and ensure teams stay on track.
+Milestones provide a layer to align work items toward shared completion dates, helping teams focus on strategic objectives and critical deliverables. Whether tracking quarterly goals, product launches, or major feature releases, milestones give you visibility into progress and ensure teams stay on track.
## Set up milestones
@@ -31,7 +31,7 @@ From your project's Overview page:
- Title: Name your milestone (e.g., "Q4 Launch", "MVP Release").
- Description: Add context about the milestone's purpose and goals.
- Target date: Set the completion deadline.
- - Link work items: Associate relevant work and epics with the milestone.
+ - Link work items: Associate relevant work with the milestone.
4. Click **Create** to save your milestone.
## Manage milestones
@@ -42,7 +42,7 @@ From your project's Overview page:
Each milestone displays:
-- Completion percentage: Based on linked work items and epics.
+- Completion percentage: Based on linked work items.
- Target date: Deadline with visual indicators for approaching or overdue milestones
Click on a milestone to expand and see all linked work items. The progress bar updates automatically as work items are completed or cancelled.
@@ -55,15 +55,15 @@ Milestones appear in the Timeline layout as vertical dashed lines at their due d
This helps you quickly identify whether work is on track to meet milestone deadlines and spot potential scheduling conflicts.
-### Link work items and epics
+### Link work items
-You can link work items and epics to milestones in two ways:
+You can link work items to milestones in two ways:
**From the milestone**
-Click **Link work items** and select work items and epics from your project.
+Click **Link work items** and select work items from your project.
-**From the work item or epic**
-Open any work item or epic and assign it to a milestone from the properties panel.
+**From the work item**
+Open any work item and assign it to a milestone from the properties panel.

diff --git a/docs/customers.md b/docs/customers.md
index db7b1dc..78faffc 100644
--- a/docs/customers.md
+++ b/docs/customers.md
@@ -100,9 +100,9 @@ Customer requests serve as the bridge between what your clients need and the act

1. From a request, click **Link work items**.
- 2. Search and select relevant Work Items or Epics.
+ 2. Search and select relevant work items.
3. Click **Add selected work items** to confirm.
- 4. In the Work item and Epic properties panel, a new **Customers** field displays all associated customers. This connection helps your teams instantly see which customers are impacted by or have requested specific work items, maintaining customer context throughout your workflow.
+ 4. In the work item properties panel, a new **Customers** field displays all associated customers. This connection helps your teams instantly see which customers are impacted by or have requested specific work items, maintaining customer context throughout your workflow.
5. Admins can hover over the **Customer** name to view details.

diff --git a/docs/dashboards.md b/docs/dashboards.md
index 550d459..de67fc6 100644
--- a/docs/dashboards.md
+++ b/docs/dashboards.md
@@ -225,7 +225,6 @@ _Options:_
- Assignees, Created by
- Labels
- Cycles, Modules
-- Epics
- Work item types
- Projects
- Start date, Due date, Created date, Completed date
diff --git a/docs/roles-and-permissions/member-roles.md b/docs/roles-and-permissions/member-roles.md
index 9b7d7dd..3a72882 100644
--- a/docs/roles-and-permissions/member-roles.md
+++ b/docs/roles-and-permissions/member-roles.md
@@ -53,13 +53,13 @@ Project roles control what a user can do inside a specific project.
### Project Admin
-Project Admin has full control over the project — settings, members, work items, epics, cycles, modules, pages, views, intake, automations, workflows, labels, states, and estimates. Project Admins can also delete or archive the project itself.
+Project Admin has full control over the project — settings, members, work items, cycles, modules, pages, views, intake, automations, workflows, labels, states, and estimates. Project Admins can also delete or archive the project itself.
Use Project Admin for project leads, managers, or anyone responsible for the project's setup and execution.
### Contributor
-Contributor is the standard project role for people doing the work. Contributors can create and edit work items, epics, modules, cycles, pages, and views. They can delete content they created themselves, but not content created by others. They can add comments, attach files, log work, and add reactions.
+Contributor is the standard project role for people doing the work. Contributors can create and edit work items, modules, cycles, pages, and views. They can delete content they created themselves, but not content created by others. They can add comments, attach files, log work, and add reactions.
Contributors cannot manage project settings, change member roles, manage labels or states, or delete content created by others.
diff --git a/docs/roles-and-permissions/overview.md b/docs/roles-and-permissions/overview.md
index 4e356ff..1c39d0c 100644
--- a/docs/roles-and-permissions/overview.md
+++ b/docs/roles-and-permissions/overview.md
@@ -40,7 +40,7 @@ Plane's permission system operates at three scopes:
```
Workspace
├── Project
- │ ├── Work items, Epics, Modules, Cycles
+ │ ├── Work items, Modules, Cycles
│ ├── Pages, Views, Intake
│ └── Labels, States, Estimates, ...
├── Teamspace ──(grants access to)──► Project
diff --git a/docs/roles-and-permissions/permissions-matrix.md b/docs/roles-and-permissions/permissions-matrix.md
index fbb7597..e8deef8 100644
--- a/docs/roles-and-permissions/permissions-matrix.md
+++ b/docs/roles-and-permissions/permissions-matrix.md
@@ -84,16 +84,16 @@ This covers project creation, discovery, and admin operations from the workspace
### Initiatives
-| Permission | Owner | Admin | Member | Guest |
-| ------------------------------ | :---: | :---: | :----: | :---: |
-| View initiatives | ✓ | ✓ | ✓ | — |
-| Create | ✓ | ✓ | — | — |
-| Edit | ✓ | ✓ | — | — |
-| Delete | ✓ | ✓ | — | — |
-| React | ✓ | ✓ | ✓ | — |
-| Add / remove epics | ✓ | ✓ | — | — |
-| Add / remove projects in scope | ✓ | ✓ | — | — |
-| Drag and drop (reorder) | ✓ | ✓ | — | — |
+| Permission | Owner | Admin | Member | Guest |
+| -------------------------------- | :---: | :---: | :----: | :---: |
+| View initiatives | ✓ | ✓ | ✓ | — |
+| Create | ✓ | ✓ | — | — |
+| Edit | ✓ | ✓ | — | — |
+| Delete | ✓ | ✓ | — | — |
+| React | ✓ | ✓ | ✓ | — |
+| Add / remove work items in scope | ✓ | ✓ | — | — |
+| Add / remove projects in scope | ✓ | ✓ | — | — |
+| Drag and drop (reorder) | ✓ | ✓ | — | — |
#### Initiative links
@@ -566,7 +566,6 @@ Third-party integration connections (GitHub, Slack, Jira, Linear, etc.).
| Permission | Admin | Contributor | Commenter | Guest | Notes |
| --------------------- | :---: | :---------: | :-------: | :---: | ------------------------- |
| Add sub-work item | ✓ | ✓ | — | — | Blocked on archived items |
-| Convert to epic | ✓ | ✓ | — | — | Blocked on archived items |
| Convert to sub-task | ✓ | ✓ | — | — | |
| Switch work item type | ✓ | ✓ | — | — | Blocked on archived items |
@@ -617,56 +616,6 @@ Third-party integration connections (GitHub, Slack, Jira, Linear, etc.).
| React to comment | ✓ | ✓ | ✓ | ✓ | |
| Resolve a comment | ✓ | ✓ | ✓ | — | |
-### Epics
-
-#### Core actions
-
-| Permission | Admin | Contributor | Commenter | Guest | Notes |
-| ----------------------- | :---: | :---------: | :-------: | :---: | ------------------------- |
-| View epics | ✓ | ✓ | ✓ | — | |
-| Create an epic | ✓ | ✓ | — | — | |
-| Edit an epic | ✓ | ✓ | — | — | Blocked on archived items |
-| Delete an epic | ✓ | Own | — | — | |
-| Archive / restore | ✓ | ✓ | — | — | |
-| Duplicate | ✓ | ✓ | — | — | |
-| Export | ✓ | ✓ | — | — | |
-| React | ✓ | ✓ | ✓ | — | |
-| Subscribe / unsubscribe | ✓ | ✓ | — | — | |
-| Convert to work item | ✓ | ✓ | — | — | |
-| Add sub-work items | ✓ | ✓ | — | — | |
-| Add / remove relations | ✓ | ✓ | — | — | |
-
-#### Epic Links
-
-| Permission | Admin | Contributor | Commenter | Guest |
-| ------------- | :---: | :---------: | :-------: | :---: |
-| View links | ✓ | ✓ | ✓ | — |
-| Add a link | ✓ | ✓ | — | — |
-| Edit a link | ✓ | ✓ | — | — |
-| Delete a link | ✓ | ✓ | — | — |
-
-#### Epic Custom Properties
-
-| Permission | Admin | Contributor | Commenter | Guest |
-| ----------------------------------------- | :---: | :---------: | :-------: | :---: |
-| View custom properties | ✓ | ✓ | ✓ | — |
-| Edit property values | ✓ | ✓ | — | — |
-| Create / delete epic property definitions | ✓ | ✓ | — | — |
-
-#### Epic Updates
-
-| Permission | Admin | Contributor | Commenter | Guest |
-| -------------------- | :---: | :---------: | :-------: | :---: |
-| View updates | ✓ | ✓ | ✓ | — |
-| Create an update | ✓ | ✓ | — | — |
-| Edit own update | ✓ | Own | — | — |
-| Delete own update | ✓ | Own | — | — |
-| React to an update | ✓ | ✓ | — | — |
-| Comment on an update | ✓ | ✓ | — | — |
-| Edit own comment | ✓ | Own | — | — |
-| Delete own comment | ✓ | Own | — | — |
-| React to a comment | ✓ | ✓ | — | — |
-
### Project Updates
| Permission | Admin | Contributor | Commenter | Guest |
diff --git a/docs/support/keyboard-shortcuts.md b/docs/support/keyboard-shortcuts.md
index e6fe5e2..edeed63 100644
--- a/docs/support/keyboard-shortcuts.md
+++ b/docs/support/keyboard-shortcuts.md
@@ -91,7 +91,6 @@ Speed up your workflow in Plane with keyboard shortcuts. Access this list anytim
| Go to home | `G` then `H` |
| Go to inbox | `G` then `X` |
| Go to your work | `G` then `Y` |
-| Go to epics | `G` then `E` |
| Go to work items | `G` then `I` |
| Go to pages | `G` then `D` |
| Go to cycles | `G` then `C` |
diff --git a/docs/templates/project-templates.md b/docs/templates/project-templates.md
index cacd511..04e0f65 100644
--- a/docs/templates/project-templates.md
+++ b/docs/templates/project-templates.md
@@ -34,7 +34,6 @@ Templates are perfect for teams who:

- - Enable or disable **Epics** based on project needs.
- You can optionally define initial work items that will automatically create when teams start new projects, helping them get up and running faster with pre-structured tasks.
6. Click **Create project template** to save.
diff --git a/docs/work-items/project-work-item-types.md b/docs/work-items/project-work-item-types.md
index 055dddd..018160b 100644
--- a/docs/work-items/project-work-item-types.md
+++ b/docs/work-items/project-work-item-types.md
@@ -5,14 +5,15 @@ description: Create specialized work item types in Plane with custom properties,
# Project Work Item Types
-Work item Types unlock a whole new way of adding, editing, and moving work forward in Plane. The default work item type called `Issue` is great for starting with Plane, but as you advance in your project management journey, you find the need for names and properties unique to the type of work you are doing.
+Every work item in Plane has a type. When you enable Work Item Types, Plane creates two types for your project automatically: **Task** (the default) and **Epic**. Work Item Types let you go further by creating named types like Bug, Story, or Feature Request with the exact custom properties each type needs.
-For example, your Marketing team may need a work item type called `Content` with the properties, `Channel`, `SEO done?`, and `Reviewer` — properties that aren't available on the default Work items. Your Engineering team, on the other hand, may want a work item type called `Bugs` with the properties `Version` and `Environment` to have more upfront info per bug reported.
+A Bug might need Version, Environment, and Steps to reproduce. A Content Request might need Channel, Reviewer, and Go-live date. A Feature Request might need Business value and Customer impact. Once you define a type, those properties appear automatically on every work item of that type.
-Work item Types make these and infinite other use cases possible.
-
-On the Enterprise Grid, work item types are managed at the workspace level for consistency across projects. See [Workspace Work Item Types](/work-items/workspace-work-item-types).
+:::info
+On the Enterprise Grid, types are managed at the workspace level rather than at the project level. See [Workspace Work Item Types](/work-items/workspace-work-item-types) for that configuration.
+:::
+
## Create work item types
::: warning
-The Work item Types feature cannot be disabled once turned on for a Plane project.
+**Work Item Types cannot be disabled once turned on for a project.** The feature itself is irreversible, though individual types can be disabled at any time.
:::
> **Role**: Project Admins
-1. Click the … icon next to your project name on the sidebar and click **Settings**.
-2. Select **Work item Types** on the right pane.
-3. Click the **Enable** button to start creating work item types for your project.
-
- 
-
-4. The default type is called `Issue`. Click the **Add Work item Type** button to create a new work item type.
+
- 
-
-5. In the **Create work item type** modal, type name, and description, and choose a background color and an icon to represent the work item type. Click the **Create work item type** button.
-
- 
-
-6. Switch on the toggle button to allow users to select the work item type when creating work items and sub-work items.
-
- 
+1. Click the … icon next to your project name on the sidebar and click **Settings**.
+2. Select **Work item Types** in the settings panel. If Work Item Types haven't been enabled yet, you'll see the option to turn them on.
+3. Click **Enable**. A confirmation prompt reminds you that this cannot be reversed. Confirm to proceed.
+4. Two types appear in the list - the default **Task** type and an **Epic** type. You can now create additional types.
+5. Click the **Add Work item Type** button to create a new work item type.
+6. In the **Create work item type** modal, type name, and description, and choose a background color and an icon to represent the work item type. Click the **Create work item type** button.
+7. Switch on the toggle button to allow users to select the work item type when creating work items and sub-work items.
### Examples of work item types
@@ -69,23 +63,17 @@ The Work item Types feature cannot be disabled once turned on for a Plane projec
- _Design agencies_
`Revision requests` `Design drafting` `Client presentation` `Quality assurance`
-- _NGOs_
- `Grant writing` `Volunteer coordination` `Beneficiary management`
-
## Add custom properties
> **Role**: Project Admins
-Adding custom properties to the default work item type Issue and other newly created work item types is possible.
+You can add custom properties to all your work item types.
1. Under the work item type, click **Add New Property** to create custom fields.
- 
+ 
2. Specify values for **Title**, **Description** and **Property type** of the new property.
-
- 
-
3. Select the **Mandatory property** checkbox if it's a required field. Select the **Active** checkbox to make the property visible in work items.
4. Click **Create** to add the property to the work item type.
@@ -105,8 +93,8 @@ Here's a list of all the property types and attributes that Plane provides for c
| **Boolean** | True/False | Default value is false. This attribute cannot be marked as mandatory. |
| **Date** | Date Format | Consistent date format across all properties. |
| **Member picker** | Single Select, Multi select | Displays a list of all project members. Members selected via a member picker property are automatically added as subscribers to the work item, so they receive notifications for updates, comments, and status changes. |
-
-| **URL** | A URL field for linking to external resources. |
+| **Release picker** | One or more releases | Multi select |
+| **URL** | | A URL field for linking to external resources. |
### Examples of custom properties
@@ -123,45 +111,40 @@ Here's a list of all the property types and attributes that Plane provides for c
Once the project Admin sets up the work item types any project member can use them when creating work items or sub-work items.
-- In the **Create new work item** modal, the user can choose the desired work item type from the list at the top left corner. By default, the work item type `Issue` is selected displaying both system-defined and custom properties.
+- In the **Create new work item** modal, the user can choose the desired work item type from the list at the top left corner. By default, the work item type `Task` is selected displaying both system-defined and custom properties.
- Changing the work item type will update the modal to display the relevant properties for that type.
- When a member picker property is filled in, the selected members are automatically subscribed to the work item. This means reviewers, stakeholders, or anyone added through a member picker stay informed without needing to be manually subscribed.
- The system ensures that all properties marked as mandatory are filled before creating the work item.
- 
+ 
When viewing work items, the work item type is displayed with an icon near the title for easy identification. Any custom properties added will also appear in the list of properties, and changes to these values are tracked in the work item's activity trail.
-## Switch work item types
+### Switch work item types
You can easily switch the work item's type at any time. Just follow these steps:
1. Open the work item you’d like to update.
2. Hover over to the right of the work item ID and click **Switch work item type**. Alternatively, you can click **Edit** from the work item's ellipsis (•••) menu to open the **Update work item** modal directly.
- 
+ 
3. Choose the new work item type from the dropdown next to your project name.
- 
-
4. Click **Update** to save your changes.
-## Bulk update work item types
+### Bulk update work item types
You can change the work item types for several work items at once. Here’s how:
-1. Switch to the **Spreadsheet** layout in the Work items page.
-2. Select the work items you want to update.
-3. At the bottom of your screen, open the **Work item type** dropdown and pick the new work item type.
-
- 
-
-4. Click **Update** to apply the changes.
+1. Switch to the **Table** layout in the Work Items page.
+2. Select the work items you want to update. A bulk operations bar appears at the bottom of the screen.
+3. Select the new type. An **Update** button appears.
+4. Click **Update**.
## Set the default work item type
-The default work item type is pre-selected whenever someone creates a new work item. Initially this is set to the built-in `Issue` type, but you can change it to any active work item type.
+The default work item type is pre-selected whenever someone creates a new work item. Initially this is set to the built-in `Task` type, but you can change it to any active work item type.
1. Navigate to **Project Settings → Work item Types**.
2. Click the **…** menu next to the work item type you want to make the default.
@@ -177,9 +160,14 @@ To remove a work item type, click the **…** menu and select **Delete**. Existi
## Disable work item types
-You can temporarily pause the creation of new work items for a specific work item type without affecting existing ones.
+Disabling a type hides it from the type selector when creating new work items. Existing work items of that type are not affected.
-1. Head to the **Work item types** screen in your project's settings.
-2. Toggle off the switch next to the work item type you want to disable.
+1. Go to **Project Settings → Work item Types**.
+2. Find the type you want to pause.
+3. Toggle off the **Active** switch next to it.
- 
+To re-enable, toggle it back on.
+
+:::info
+The default type cannot be disabled.
+:::
diff --git a/docs/workspaces-and-users/search-workspace.md b/docs/workspaces-and-users/search-workspace.md
index ce80de2..61218d7 100644
--- a/docs/workspaces-and-users/search-workspace.md
+++ b/docs/workspaces-and-users/search-workspace.md
@@ -19,12 +19,11 @@ Type your query and results appear instantly, organized by type. Use the tabs at
- **All** - Shows everything across all categories
- **Projects** - Your workspace projects
-- **Work items** - Tasks across projects
+- **Work items** - Work items across projects
- **Cycles** - Project cycles
- **Modules** - Project modules
- **Views** - Saved views
- **Pages** - Project pages
-- **Epics** - Epics in projects
- **Teamspaces** - Teamspaces
- **Comments** - Work item comments