Currently, third-party app macros created using the Atlassian Forge UI Kit or Custom UI can't be sorted or filtered based on their text content when placed inside native Confluence tables. This limitation prevents users from organizing or analyzing table data that includes Forge macros.

A common scenario is placing statuses, dates, or other dynamic information provided by Forge macros into a Confluence table to track the progress of tasks or initiatives. However, since these macros cannot be sorted or filtered, users are unable to efficiently manage or review this information within the table.

Users cannot sort or filter table rows containing Forge macros, which limits the usefulness of tables for reporting and tracking.

Currently there's no workaround available for this limitation.

We would like to request that sorting and filtering functionality for third-party Forge app macros be supported in native Confluence tables, similar to how native text or date fields can be managed.