Changelog

Stay updated with Page subscriptions

You can now subscribe to Pages and receive email notifications when someone starts a new editing session or adds a comment.

• Subscribe to Pages
  Follow an important page directly from its header, and unsubscribe whenever you want.
• Manage subscribers
  Add or remove eligible members from a Page's subscriber list.
• Follow conversations automatically
  Editing a page, adding a comment, or being @mentioned can automatically subscribe you to that page.
• Get notified of updates in your email
  Every time a page gets updates, subscribers receive a notification by email.

For example, subscribe to a product requirements Page to stay informed as the team updates specifications and discusses implementation decisions.

Create dashboard widgets directly in Pages

You can now create dashboard widgets directly from Pages, without having to set them up in Dashboards first.

Select the Widget block using the / menu, choose a chart type, and configure its data, filters, and groupings directly in the editor.

For example, create a chart showing work items grouped by state within a release planning Page to track delivery progress alongside release requirements and checklists.

Your work items now show the code being written for them. The new Development panel brings linked Git branches, commits, and pull or merge requests into the work item, making it easier to follow implementation and review progress without searching through your repositories.

Track development activity alongside your work

Open a work item and expand the Development section to see the Git activity associated with it.

• Branches: See linked branches, organized by repository, along with commit counts and associated pull or merge requests.
• Commits: Expand a branch to review its commits, including messages, authors, and timestamps.
• Pull and merge requests: Check request titles, review and merge status, target branches, changed files, and additions or deletions.
• CI status: Review available checks, pipelines, or build status reported by your connected Git provider.

The section uses each provider's terminology, including pull requests for GitHub and Bitbucket and merge requests for GitLab.

Link Git activity to work items automatically

Plane uses work item references to associate Git activity with the corresponding work items.

For example, name a branch feat/WEB-344-checkout-validation. Once the connected integration syncs the activity, it appears in the Development section of WEB-344.

The Development section is read-only. To make changes to a branch, review code, or merge a pull request, open it in your Git provider.

Availability

Git development activity is available on Plane Cloud, starting with Pro, through supported GitHub, GitLab, and Bitbucket integrations.

Custom properties can now follow a hierarchy. Introducing Cascading, a new property type that lets you create dependent dropdowns where each selection determines which options appear next.

Define up to four connected levels to capture detailed information while keeping the available choices relevant to the work item.

Create dependent dropdowns with up to four levels

Build a Cascading property with two to four levels, each containing its own set of options.

For example, create a Customer issue property with four levels: Topic → Area → Problem → Payment method. Select Billing → Payments → Charged twice → Credit card to categorize a duplicate payment issue.

Each choice follows the dependent options you've configured, preventing selections that don't belong together.

Make specific levels mandatory

Mark individual levels as mandatory when your workflow requires additional information.

For example, you can require both Product and Component in a product classification hierarchy. Making a deeper level mandatory also makes its preceding levels mandatory.

If a selected branch has no options at a mandatory level, Plane skips that level rather than blocking work item creation.

Availability

Cascading custom properties are available on Plane Cloud on Enterprise Grid.

Some work needs more restricted access, even within a shared project.

Introducing Work item security, which lets you control who can see sensitive work items using Audiences. Restrict an individual work item or apply the same access rules to an entire Work item type, while keeping the work in its existing project.

Define access with Audiences

An Audience is a reusable group that determines who can view restricted work items. Create audiences at the workspace level using:

• Workspace roles
  Include members based on their workspace permissions.
• Project roles
  Include members based on their roles within a project.
• Specific members
  Grant access to individuals, regardless of their role.

You can combine these criteria within an audience and review its effective membership before applying it.

Workspace owners and admins always retain access to restricted work items. Work item assignees and subscribers also retain access, even when they aren't included in the selected audience.

Restrict individual work items

Apply an Audience to a specific work item when its contents should be visible only to selected people.

For example, a project may contain a confidential budget approval that requires review by Finance and leadership. Apply the appropriate Audience to keep that work item restricted without moving it into a separate private project.

Apply security to entire Work item types

For categories of work that regularly contain sensitive information, apply Audiences at the Work item type level.

For example, create a Security Incident Work item type and assign a Security Audience to it. Every work item of that type follows the configured visibility restrictions.

Multiple Audiences can be attached at either level. Anyone matching at least one active Audience at the applicable level can access the item.

Keep restricted work visible only to authorized people

Restricted work items are excluded from the surfaces available to people without access, including:

• Project lists, boards, cycles, and modules.
• Dashboards, Pages, and search results.
• Notifications and emails associated with the restricted work item.
• Direct access to the work item's contents and attachments.

Authorized members see an indicator on restricted work items, making it clear that their visibility differs from other items in the project.

Audiences control visibility. Existing workspace and project permissions continue to determine what authorized members can do with the work item.

Availability

Work item security is available on Plane Cloud on Enterprise Grid.

A new way to organize structured information inside Plane Wiki and Pages.

Build spreadsheet-style tables with custom properties, filters, sorting, and linked work items. Keep checklists, inventories, decision logs, and other structured records alongside the documentation they support.

Create databases inside Pages

Add a Database block to a Page using /database and start organizing information into rows and columns. Each row represents a record, and each column holds a property. You can add Databases to Wiki, project, and Teamspace Pages.

Customize your columns

Choose the properties that make sense for the information you're tracking.

• Text and numbers
  Record descriptions, quantities, costs, and other values.
• Dates and checkboxes
  Track deadlines, completed actions, and confirmations.
• Single-select and multi-select
  Categorize records with predefined options.
• People
  Associate one or more workspace members with an entry.
• Work items
  Link records to work items from across your workspace.
• URLs and email addresses
  Keep references and contact details accessible.

Filter and sort your data

Find the information you need without scanning every row.

• Filter
  Narrow down records using property values and multiple conditions.
• Sort
  Arrange records in ascending or descending order.

Availability

Databases is available on Plane Cloud on Enterprise Grid.