Feature ideas

At the moment you cannot run additional filters on calculation property. This makes creating widgets or charts impossible for those properties.

Bar charts should support a timeline on the X-axis. Today, bar charts are mainly used for grouping properties, but it would be very valuable to also use them to present data over time. Currently, the only way to visualize this is with a line chart, which isn’t always ideal or intuitive, especially when there are gaps in the data, making the chart harder to interpret. Screenshots show the expected bar charts behavior vs the line chart behavior that is supported today.

Use AI to generate an on demand report in Port. The report is built from Port’s context lake and answers a specific question or analysis need, for example a manager asking for a quick snapshot of ownership, risk, progress, or gaps across teams. Unlike a dashboard, this is a report, not saved in the sidebar and also not limited to ports widgets. Users can generate it ad hoc, then export or share. See a few ideas for mock-ups.

Currently, dynamic URLs in the Links Widget are only supported on specific entity pages using the entity identifier (e.g., {{url.identifier}}). We request expanding this capability to allow dynamic URL mapping in all dashboard contexts, enabling more flexible and context-aware navigation for users. This would allow, for example, dashboards to display links that adapt based on the current context or selection, not just on entity pages.

Add support for breaking down by property in a pie chart for calculation properties, scorecards, and scorecard rules

🔎 Context We are integrating multiple infrastructure and operational data sources into Port, for example: Component (title, mentor, status) <- App Version (title) <- EKS Workload (cluster, aws account, containers) -> Environment (title) Component <- App Version <- ECS Task Definition -> Environment Component <- App Version <- ArgoCD Application -> Environment We have already connected all required infrastructure data sources to Port, so the deployment data is available in the catalog. However due to current reporting limitations it is difficult to transform this data into useful operational dashboards. 💡 Possible solution Provide dashboards / reports that allow: 1️⃣ Using attributes from multiple related entities see related idea https://roadmap.getport.io/ideas/p/allow-mirror-properties-to-be-defined-using-a-relation-path 2️⃣ Grouping columns by values from related entities Allow building matrix-style reports, where grouping is based on entity attributes. Example: Rows grouped by Component.title Columns grouped by Environment.title 3️⃣ Cells showing attributes from related entities Inside each cell we would display: App Version.title with the ability to expand additional details such as: Component (mentor, status) EKS Workload (cluster, aws account, containers) Example layout: Component trunk preprod prod service A serviceA:1.2.4 serviceA:1.2.3 serviceA:1.2.2 service B serviceB:1.1.4 serviceB:1.1.4 serviceB:1.1.4 Example to expand additional details in cell: Component trunk app version=serviceA:1.2.4, service A mentor=User1, status=retired, cluster=cluster1, aws account=123456, containers=... 📈 Impact As a result, we are not able to use Port’s native visualization capabilities and are forced to build external data views and reports. This makes the work more complex for architects and support teams and requires additional development and infrastructure resources, which contradicts the key advantages of using a SaaS platform.

The ability to add buttons at the top of pages such as the Homepage or Catalog dashboards. These buttons could link to documentation or other key resources. The goal is to provide high-visibility entry points for common information so users don’t need to search through Markdown sections or navigate multiple pages. Having consistent buttons in a fixed location across pages would make it easier to train users and improve discoverability and adoption of key platform capabilities. (Similar to how we have a button in our demo in the Self-Service Hub that directs to documentation links)

Add the ability to control the data being analyzed at multiple levels (all data, dashboard level, and widget level). When reviewing row-level data behind metrics, there are certain users or use cases that need to be filtered out to see the correct metrics for example automated users. The request is to allow more granular filtering so teams can exclude specific data points when analyzing metrics and row-level data.

As for now the API route for pages and Sidebars are very complex (and it's still in beta), we need to have a better implementation for it

A widget that could be used to track the TTLs and other time/date events. Could be useful for tracking upcoming events such as maintenance windows, Ephemeral Environment expiration, Sales Demo expiration, etc.. Dots could appear on the day of the event and clicking on that day would zoom in and show the entities and current TTL or date stamp. Allow it to filter which date/time properties to display.