Workspace Work Item Types Enterprise Grid

On the Enterprise Grid, work item types are defined at the workspace level by Workspace Admins and imported into projects.

This ensures consistency — a "Bug" in one project has the same properties and structure as a "Bug" in another — while keeping centralized governance over how work is tracked across your organization.

INFO

On Pro and Business plans, work item types are managed at the project level. See Project Work Item Types.

How workspace work item types work

Every workspace starts with a default type called Task. This is the base type for all work items and cannot be deleted. You can add custom properties to it, but it's always available as a fallback.

When you create additional types at the workspace level, they don't automatically appear in projects. Project Admins import the types they need from the workspace library, making only the relevant types available in their project. This keeps projects focused while maintaining centralized governance.

The type assigned to a work item determines its available properties and its behavior across workflows. Changes made to a type at the workspace level reflect across all projects using that type — there's no duplication.

TIP

If you had work item types configured at the project level before upgrading to the Enterprise Grid, they've been rolled up to the workspace level. Project Admins can no longer create or edit types directly — that's now handled by Workspace Admins. Your existing types and properties are preserved and available in the workspace library.

Activate workspace work item types

WARNING

Work item types cannot be disabled once enabled for a workspace.

Role: Workspace Admin

1. Go to Workspace Settings > Work item Types.
2. Toggle on Turn on Work item types for this workspace.

Once enabled, you'll see the Work item Types and Properties tabs. The default Task type is already listed.

Create workspace work item type

Role: Workspace Admin

1. On the Work item Types tab, click Add work item type.
2. In the modal, enter a unique name and a description that explains what this type is for and when to use it.
3. Click the icon to the left of the name to choose a custom icon and color.
4. Click Add work item type.

The new type appears in the list. Use the toggle next to it to control whether project members can select it when creating work items.

Create workspace custom properties

Role: Workspace Admin

Custom properties are fields you define at the workspace level and attach to one or more work item types. A property like "Severity" can be used across both "Bug" and "Incident" types without duplicating it. Properties are not automatically applied to all types — you explicitly choose which properties belong to which type.

Create a property

1. Switch to the Properties tab.
2. Click Add new property.
3. Fill in the Title and Description.
4. Select a Property type from the dropdown.
5. Check Mandatory property if this field should be required when creating a work item of the linked type.
6. Click Create.

The property is now available to attach to any work item type.

Attach properties to a type

1. Switch to the Work item Types tab.
2. Expand the type you want to add properties to by clicking its arrow.
3. Click + Add properties.
4. In the modal, select the properties you want to attach and click Add.

If the modal shows "No properties available," either all existing properties are already linked to that type, or no custom properties have been created at the workspace level yet. Create new properties from the Properties tab first.

Property types

Property type	Description
Text	Single line or paragraph text. Can be set to read-only with a default value. Read-only properties cannot be marked as mandatory.
Number	Numeric value with an optional default.
Dropdown	Single-select or multi-select from a defined list of options.
Boolean	True/false toggle. Defaults to false. Cannot be marked as mandatory.
Date	Date picker with a consistent format across all properties.
Member picker	Single-select or multi-select from the list of project members.
Release picker	Select from available Releases in the project.
URL	A URL field for linking to external resources.

Import types into a project

Role: Project Admin

Projects don't create their own types — they import what's defined at the workspace level. Imported types are linked to the workspace definition, so updates made by Workspace Admins are reflected automatically.

1. Go to Project Settings > Work item Types.
2. Click Import from workspace.
3. In the modal, select the types you want to bring into this project from the workspace library.
4. Click Add.

The imported types now appear in the project's type list alongside the default Task type. Project members can select them when creating work items.

Only types that have been imported into a project are available when creating or editing work items in that project.

Use workspace work item types

Once types are available in a project, any project member can use them.

When creating a new work item, select the type from the dropdown at the top-left of the create modal. The modal updates to show the properties associated with that type. Any mandatory properties must be filled before the work item can be created.

When viewing work items, the type is displayed with its icon next to the work item title. Custom properties appear in the properties panel, and changes to property values are tracked in the work item's activity trail.

Switch a work item's type

1. Open the work item.
2. Hover to the right of the work item ID and click Switch work item type. Alternatively, click Edit from the work item's three-dot menu.
3. Choose the new type from the dropdown.
4. Click Update.

Bulk update types

1. Switch to the Spreadsheet layout on the Work items page.
2. Select the work items you want to update.
3. Open the Work item type dropdown at the bottom of the screen and pick the new type.
4. Click Update.

Disable a workspace work item type

Role: Workspace Admin

You can temporarily prevent new work items from being created with a specific type without affecting existing ones. On the Work item Types tab, toggle off the switch next to the type you want to disable.

Existing work items of that type are unaffected — they retain their type and properties. The type simply won't appear as an option when creating new work items.

Delete a workspace work item type

Role: Workspace Admin

Deleting a type removes it from the workspace library and from every project that imported it. Existing work items of that type will need to be reassigned to another type.

Before deleting, consider whether disabling the type would be a better option — it preserves existing work items while preventing new ones from being created.

Hierarchy

Hierarchy lets you define structured parent-child relationships between work item types at the workspace level.

Once configured, it controls which types can be nested under which — ensuring that work is organized consistently across every project in the workspace.

Without hierarchy, any work item can be a sub-work item of any other, regardless of type. With hierarchy enabled, Plane enforces the rules you define: an Epic can only contain Stories and Tasks, a Campaign can only contain Deliverables, and so on. Invalid nesting is blocked throughout the product.

Why use hierarchy

Hierarchy is useful when your organization has a clear structure for how work breaks down and you want to enforce it consistently. It prevents ad hoc nesting that doesn't match your process, keeps reporting and rollups meaningful, and makes it clear to everyone on the team what "level" of work they're looking at.

How hierarchy levels work

Hierarchy is organized as numbered levels, where higher numbers represent broader work and lower numbers represent more granular tasks. Each level can contain one or more work item types, and each level defines a parent relationship with the level directly above it and a child relationship with the level directly below it.

Level 0 is the default — types that sit here are leaf-level work items with no children defined in the hierarchy. Types not assigned to any level remain at Level 0.

For example, a product engineering team might define:

Level	Types	Role in the hierarchy
2	Epic	Major feature or deliverable
1	Story, Bug	Individual units of work
0	Task, Spike	Leaf-level execution items

In this setup, an Epic can contain Stories and Bugs, and a Story can contain Tasks and Spikes. But a Task cannot contain an Epic — the hierarchy enforces the defined structure.

Activate hierarchy

WARNING

Hierarchy cannot be disabled once enabled for a workspace.

Role: Workspace Admin

Hierarchy requires work item types to be activated and defined first.

Once enabled, you'll see all your work item types listed at Level 0 (Default), with a drop zone above for building levels.

Configure hierarchy levels

1. Drag and drop a type from Level 0 up into a new level to create the hierarchy. Each type you drag creates or joins a level.
2. Levels are numbered automatically — higher numbers sit at the top of the hierarchy.
3. Multiple types can sit at the same level. For example, Bug and Customer feedback can both be Level 2 types, meaning both can serve as parents to Level 1 types.
4. Use the … menu on a level to set it as default.
5. Click Save changes when you're done. Click Discard to revert unsaved changes.

The hierarchy builder shows the parent→child flow with arrow connectors between levels, making it easy to visualize the structure.

What hierarchy enforces

Once hierarchy is enabled and configured, the following rules are enforced across the workspace:

Work item creation. When creating a new work item, the type dropdown reflects hierarchy rules.

Sub-work item creation. When adding a sub-work item to a parent, only types from the level directly below the parent's level are shown. Disallowed types are automatically hidden from the picker.

Type changes. If a work item already has parent or child relationships, changing its type is only allowed if the new type is valid within the existing hierarchy. If the change would create an invalid relationship, it's blocked.

Data integrity. Hierarchy prevents invalid parent-child mappings from being created through any surface — the UI, bulk operations, or imports. Existing relationships that were created before hierarchy was enabled remain intact, but new invalid relationships cannot be added.