Feature ideas

In order to make it easy to re-use the structure of a dashboard page, an option to duplicate a dashboard page can really help

Within the guides on the Port documentation site, there is a UI component that can be used to display code snippets (offering line number display, syntax highlighting and a copy button for easy reuse). Backstage offers a code snippet component for use within their portal (also offering conditional line number display, language-specific syntax highlighting, a built-in copy button, and automatic dark mode support). Similar to these examples, we would like a code snippet widget (similar to the existing markdown widget, though with it's source as a markdown property on the current entity - similar to this feature request ) that includes the following: line number display (turn on/off with a widget property, default to on?) syntax highlighting (language specific, based on a language added to the markdown-based code block - something like ```js - when that annotation exists) built-in copy button (just like the snippets in the Port docs site) ----- Our intended use case centers around helping developers connect the dots in the software development lifecycle between "paved roads"/"golden paths" (fully templated project starting points) and finished product (pull requests leading to deployed code) - the ability to share reusable code snippets that both promote best practices and help give newer developers additional lift. We envision this overall functionality would include a blueprint with code snippet entities, a catalog page to allow users to search/filter/sort to find the snippet they are looking for (or to just browse through available snippets for inspiration), and then a code snippet entity page displaying an entity widget with details about the snippet (title, description, language, tags - this feature request would help with that piece a lot!, etc.) and this new code snippet widget allowing the developer to both see the snippet in a well-presented manner (line numbers, syntax highlighting, etc.) and use a built-in copy button to quickly and easily grab the snippet for pasting into their IDE. Looking towards day 2, we also hope to explore using Port's MCP server for direct IDE integration, allowing a user to try to find and pull in applicable snippets directly. I could also see applicability for some of the same functionality within rendered markdown files (automatically parsing and rendering code blocks with line numbers, syntax highlighting, and a built-in copy button within an imported markdown file - like where we pull in README.md files for repos and display them in a markdown tab on the repo entity page)...but that feels like a separate request.

Current behavior: Once the table is grouped by criteria, all scores/enums receive a quantity visualization of proceeding values under the group. However, for numeric properties, nothing is displayed. Suggestion: For grouped numeric properties, reuse this empty space to provide a user-selected metric (e.g., average, median, etc.).

Current Behavior Any property or score (including rules) added to a blueprint automatically appears under all card widgets within that blueprint’s entity page views. Issue I have blueprints with entity page views containing multiple configured cards that group properties for different purposes. When a new score or property is added to an entity, all of those cards are instantly prefilled with the data. This results in unnecessary clutter and confusion across the cards. Suggestion Hide all properties by default, as was done under tables ( https://roadmap.getport.io/ideas/p/property-exclusion-in-tables ). Alternatively, allow the user to choose whether a new property or score should appear under widgets.

It would be helpful to have the option for Automations to automatically handle errors and retry runs whenever the initial execution fails due to backend issues. This would improve reliability and reduce the need for manual intervention in transient failure scenarios.

Current behavior Numeric values are displayed as plain text below the table. When a table contains many numbers (across both entities and properties), it becomes hard to identify the “problematic” value that needs closer inspection. Proposed solution While scorecards can achieve a similar effect, it’s also helpful to see which specific value drives a score up or down. I suggest adding an additional property to numeric fields that lets us declare a color indicator. This would visually highlight values that require attention and make it easier to spot outliers directly in the table.

Bring your own MCP. Port’s AI today only sees what’s inside Port. By bringing in a customer's MCP Server and their AI Agents, they are already pulling in external context from Confluence, Jira, and other systems. Their AI Agents may have deep context surrounding their business. Customer wants Port to be able to tap into that external intelligence so the AI inside Port can act with full awareness of both Port and non-Port data.

Port currently provides only regular widget for table representation, which makes it difficult to compare values across different properties. By adding a Pivot/Matrix view, users could select one property to serve as column headers, while the remaining properties stay as rows. If multiple entities share the same value of the selected property, their values could be aggregated (avg, min, max, sum). This structure would enable clear side-by-side comparisons across all properties, making patterns and relationships easier to see. Additionally, a heatmap option could highlight high/low values visually, further improving insights without needing external tools.

Currently, webhook data source cards display all blueprints that have ever been successfully ingested through them. Even after the mappings for certain blueprints are removed, those blueprints continue to appear in the data source card. This can cause confusion and unnecessary clutter, as the card no longer reflects the active mappings. It would be much more helpful if the card displayed only the currently mapped blueprints, ensuring that the information remains up to date, and relevant.

Problem Statement: In some environments, the Port Agent must communicate with services secured by non-standard or private certificate authorities. Currently, there is no straightforward way to mount custom CA certificates into the agent container when deployed via the Helm chart. This limitation makes it difficult to operate in environments with custom security requirements. Proposed Solution: Extend the Port Agent Helm chart to allow users to specify additional volumes and volume mounts. Provide an example configuration to demonstrate mounting a secret or ConfigMap containing custom CA certificates. Ensure the agent container recognizes and utilizes the mounted certificates for outbound communication. Benefits Enables secure communication with services protected by private or non-standard CAs. Improves flexibility of Port Agent deployments in enterprise and regulated environments. Reduces the need for manual workarounds or custom image builds. Example Values.yaml with extra volumes extraVolumes: - name: custom-certs secret: secretName: custom-ca-secret extraVolumeMounts: - name: custom-certs mountPath: /etc/ssl/certs/custom readOnly: true