Feature ideas

Support creating self-serive actions from Port MCP. In this roll out of version 0.2.15, bringing CRUD support for actions—a major step forward on our path to fully enabling Vibe Building. In this video, I am vibe building using our guides and end-to-end with the

Create a UI for additional filters on widgets instead of requiring users to define them manually in JSON, making the configuration process more intuitive and accessible.

We will improve our interface for Automation (to match with one of Actions) to simplify the creation of new automation. Some early preview screenshots are attached!

Provide users with an at-a-glance view of what happened during the last sync, including high-level statistics (raw objects, transformed objects, success/failure count), sync duration, and time of last run. This allows users to assess sync behavior without diving into raw logs, improving usability and reducing support load. See prototype here - https://effulgent-nasturtium-76fd8f.netlify.app/ Similar FRs https://roadmap.port.io/ideas/p/expose-metrics-from-ocean-integrations https://roadmap.port.io/ideas/p/data-source-heartbeat-monitoring

Context With a one-to-many Relationship in Blueprint A to Blueprint B, one can add a Mirror Property. If an Entity in A is related to an Entity in B, it will show that property of B in A. If that property in B is a String, it will appear in A as a String; if it is a Number in B, it will display as a Number in A. In Port a Property can have a number of Data Types, among which String, Number, and DateTime. But a Property can also be an Array of Strings, an Array of Numbers, or an Array of DateTime. Request Make it possible to create Mirror Properties on many-to-many Relationships as well. With a many-to-many Relationship in Blueprint A to Blueprint B, one can add a Mirror Property. If an Entity in A is related to Entities in B, it will show a list of values of that property of B in A. If that property in B is a string, it will appear in A as an Array of Strings; if it is a Number, it will display as an Array of Numbers.. Edge Cases If the Property in B is already an Array of Something, there is an issue, because that would become an Array of an Array of Something in A, which is a data type that Port currently doesn't support. With Relations there is a higher potential for a large number of items that would end up in the Mirror Property in A. Currently Port only supports Arrays of Strings, Numbers, and Objects. That may limit the data types for which a Mirror Property for a many-to-many Relationship can be created.

As part of Azure DevOps ocean integration, support mapping each folder as a separate entity

When a widget doesn't have data, it is displaying "No data for this widget". We would like to be able to set our own text when that happens, so the user knows what to do next

The SSO flows are a bit awkward since they have to be initiated by the IdP at the moment. Adding SCIM support would allow us to configure third-party Identity Providers such as Okta, Auth0, or Azure AD to provision users and groups in our Port accounts, allowing users to authenticate through Port rather than initiating login through the Identity Provider.

We would like to add the ability for the line chart to aggregate and display entities' history over time, in addition to the existing capability to display the history of a single property. For example, this will allow ingesting into Port an entity for each deployment and display the amount of weekly/monthly deployments in the line chart.

For long forms, I sometimes want to add a bit more context for upcoming inputs or add some visual separation between inputs on the same step. It would be great to be able to insert some text on its own in a form.