Feature ideas

Add ability to create widgets with graphs or charts where a user can edit drilldown data and set events on click as to open a table or show another graph/chart of more granular data

Allow to trigger and approve actions from the MCP server to enhance the integration for both developers and agents

Currently, the webhook integration does not allow you to reingest failed events, or recover from incidents with the integration. Implementing a Dead Letter Queue or an alternative mechanism that lets you redeliver events received by the webhook integration will improve the integration resiliency.

Today, Port Automations will not be triggered upon deleting related entities or updating the value of a mirror property of an entity. But it would be beneficial if it were possible.

The automation feature in Port allows users for event driven actions. At the moment, this feature allows users to take only one action at a time such as updating an entity, calling an external API, invoking an action. It would be possible if users can define a series of steps in the invocationMethod such that once an automation is triggered, it will follow the steps and complete the entire workflow. At the moment, if my use case involves making two API calls to an external tool, updating the catalog, automations aren't able to help so I would resolve to using a GitHub action for this complex use-case

Change request and ITOM assets

The scoreboard order keeps on changing even if we arrange in the json.. or in other words there is no way to order the scorecards in the way we want.

Today you can add additional filters via JSON to any table, chart, etc using some of the intrinsic functions like: "getUserTeams()". With the ability to customize the user data-model (like a profile), it would be beneficial to access other user data properties to filter on that we added custom. Perhaps a new function like: getUserProperty("myCustomProp") to use in rules: { "property": "github_user_id" "operator": "=", "value": "getUserProperty('my_github_user_id')", }

For some kinds available in integration, the API responses can vary greatly depending on certain conditions. As a concrete example, in the github integration, the branch kind only contains properties like .branch.commit.commit.author when the branch is the default branch of a given repository, and in my mapping I set the query to .branch.name == .repository.default_branch to ensure I have access to that value. What I'm currently finding is that the sendRawDataExamples option in integrations does not respect this query setting, so the ~5 examples retained from the api call might not even contain a valid api response (as in, one that passes the check in query ). I have a few varied suggestions here: Allow sendRawDataExamples to respect the given query in a mapping. Allow sendRawDataExamples to have it's own query for stricter or looser example api responses. Allow independent resync of sendRawDataExamples separate from a resync of the data source. Giving builders the ability to have stronger control over the examples defined in the data source view would significantly improve iteration time when dealing with complex mappings across multiple data sources.

Currently number fields don't have any formatting options. It would be nice to be able to declare how each numeric field should be displayed, e.g. the number in the picture would be nicer written as 13,850,834. Currency signs and decimal places would also be useful. https://cloud.google.com/looker/docs/custom-formatting Looker has good support for this as an example.