Introducing a new workspace-level Release that groups work, tracks delivery, and publishes the changelog, plus four advanced property types that let work items carry the kind of structured data they couldn't before.

What's shipping

• Releases
  A workspace-level artifact that pulls work items from any project under a named version, tracks completion, and publishes a changelog when it ships.
• Advanced custom properties
  Two new property types for work items: Release picker, Formula field

1. Releases

Releases give your workspace a place to group work items under a named version, track progress, and publish what changed when you ship. Cross-project by design: a single release can pull work items from any project in the workspace, useful when a feature launch involves work across multiple teams.

How to set up
Workspace Settings → Releases. Toggle Enable Releases. The section appears in the workspace sidebar for all members. Disabling hides the section but preserves all data; re-enabling restores everything. Workspace Admin role required.

Set up tags and labels first (optional, worth doing). From the same settings page:

• Release tags categorize releases across the workspace, and are useful for filtering by type, environment, or team.
• Labels organize releases visually with name and color. Separate from project-level work item labels.

To create a release,
Click Releases in the workspace sidebar and select Add Release. A Title is required, while the Description, Status, Tag, Labels, Target date, and Lead are optional.

A release progresses through three key statuses,

• Unreleased, the default. Work is still in progress; the scope and changelog are being built.
• Released. The release has shipped.
• Cancelled. The release was abandoned. Scope and history are preserved without cluttering active releases.

The Releases list groups by status, so the active list stays clean.

Three tabs per release:

• Overview shows the description, selected properties, and a live progress tracker. The progress bar fills proportionally as work items complete (e.g., 18/22, 82%). Counters display completed, pending, and canceled work items. Click any property chip (Tag, Label, Lead, Target date) to edit inline.
• Scope lists every work item attached to the release, categorized by state group. Click Add work items to search and attach by title or ID. Work items from any project in the workspace can be scoped. A work item's existing state automatically drives the progress calculation; nothing needs to be marked as "done in release" separately.
• Changelog is a rich-text editor that supports the same blocks as Pages and Wiki. Autosave. Visible to every workspace member who can access the release.

Use Scope to audit completed work items. Use Changelog to write user-facing notes from that list.

2. Advanced custom properties

Plane already ships seven property types for work item types: Text (single line, paragraph, read-only), Number, Dropdown (single, multi), Boolean, Date, Member picker, URL. Member picker has a useful side effect: members selected via a member picker property are auto-subscribed to the work item, so reviewers and stakeholders stay in the loop without manual subscription.

The two new types extend that foundation.

1. Release picker
   A property that points at a Release. Adding it to a work item type is a Project Admin action: Project Settings → Work item Types → select the type → Add custom property of type Release.

• Once added, the Release picker field appears in the work item detail view. Any project member can set which release a work item belongs to directly from there, and the work item automatically appears in that release's Scope tab.
• With release as a property, you can group, filter, and build dashboard views around release milestones, giving leadership visibility into delivery velocity per release.

2. Formula field
   A property whose value is computed from other properties on the same work item. Useful when the data your team needs is a function of fields you already track, not something members should enter manually.

Availability across plans

Read the docs. Releases, Project work item types.