Tables now provide a more polished grid experience with improved interactions and alignment, making information easier to scan and work with.

: Teams working in table-based views can review and edit structured information with a clearer, more consistent layout.

Dashboards can now surface planned dates together with actions, giving teams more scheduling context while reviewing work.

Teams using dashboards to monitor planned work can see action timing alongside the work itself.

My Actions now includes actions assigned to you from other workspaces, bringing those assignments into one personal view.

: People who work across multiple workspaces can review their assigned actions in one place.

Notifications now support comments and reactions, making it easier to respond to activity and acknowledge updates in context.

You can add a reaction from Workspace Activity or the Project overview page.

Teams using notifications to follow work can respond and share lightweight feedback without leaving the activity feed.

Buzz can now distinguish between messages meant for people and messages that call for Buzz. In shared threads, it stays quiet when one person is speaking to another, while responding to open-room questions and clear follow-ups addressed to Buzz.

Explicit @Buzz mentions continue to trigger a response. This keeps shared conversations focused while making it easier to get help when you need it.

Teams collaborating in shared threads get fewer interruptions and more relevant Buzz responses.

Workspace admins can now filter Action Card Statuses by project and combine the project selection with status search. The matching status list updates to the selected project, while the Used in count continues to reflect every accessible project where each status is used.

In Workspace Settings, open Custom Statuses → Action Card Statuses and select a project from the new filter.

This helps workspace admins manage large, project-specific status libraries faster without losing the broader usage context for shared statuses.

Forms can now use a Table as a data source. Form creators can map Table columns to form fields, and selecting a Table record can prefill the mapped values while keeping them editable when the form configuration allows it.

In the Form Creator, configure a Table source and field mappings. People completing the form can then select a Table record to populate the mapped fields.

This helps teams that manage reusable reference data, such as vendor details, collect consistent information without asking submitters to re-enter known values.

Table and Gantt now support entering predecessors with flat, visible row numbers, including visible subactions in nested project plans. Existing WBS-style predecessor references remain supported, and WBS display stays the default unless the row-number display option is enabled.

Enter a visible row number in the predecessor field in Table or Gantt. Enable the row-number predecessor display option in the view when you want predecessor columns to use flat row numbers.

This helps project planners and teams building nested templates create dependency chains with simpler references while keeping existing WBS-based plans compatible.

Buzz on mobile now uses two levels of back navigation. Going back or swiping from a conversation returns to the Buzz thread list first, while a separate Back to Hive action exits Buzz.

Open a Buzz conversation on mobile, then use the back gesture or control to return to your thread list. Use Back to Hive when you are ready to leave Buzz.

This helps mobile Buzz users move between conversations without accidentally leaving Buzz and makes the exit path clearer.

Gantt project rows can now reflect a project's configured start and end dates, even when the project has no dated child actions. When dated child work extends beyond the project range, the row spans the combined period, preserving the existing rollup while making project-level dates visible.

Open a project in Gantt view to see its project dates reflected on the project row alongside dated child work.

This helps project managers and portfolio teams compare the planned project window with the underlying schedule more clearly.