Feature ideas

Currently the Azure DevOps pipeline metadata that is ingested lacks context of the originating repo. The Azure DevOps API for pipelines is capable of returning a configuration object which contains all the necessary repository data. This will allow for easier linking of pipelines to repositories.

Expose an MCP of Port with tools LLMs and AI Agents can use to interact and get information from Port

The ability to add custom headers that will be applied for the entire API spec. So that as a Port member, I will be to step into a service API spec, add a custom header once and it will be applied for all of my API routes in the API spec.

The https://demo.getport.io/organization/home dashboard currently includes a series of "Quick Access" links. While these can be crafted via HTML within a markdown widget, the outcome has several limitations: We cannot tailor the view to show/hide links based on which pages the user has access to (RBAC) We cannot re-use the same iconography that is used on blueprints/entities - see https://roadmap.port.io/ideas/p/add-the-ability-to-access-icons-images-within-markdown-widgets Styling the widget in general is possible, but requires a lot of hand-cranked inline CSS The suggestion here is to offer this as a new widget type - one which dynamically builds content based on: What pages are available in the catalogue What pages the current user has access to Icons used on each of the available pages Ideally, we'd also have a way for either: Users to mark a page as a "favourite" - and the widget only shows this subset The widget picks out pages which are used most frequently ...but I suspect this last part is a separate feature :)

Currently, you cannot assign roles to SSO groups. This means that whenever a new user is logging in, you need to assign it the roles. Having the possibility to assign roles to groups will enable us to manage user permissions on groups level through the SSO.

Currently, time-based configurations require manual updates when daylight saving time (DST) changes. This feature request proposes an enhancement to enable the system to automatically adjust for DST without requiring manual modifications. Implementing this would ensure accurate time calculations, reduce the risk of errors, and eliminate the need for repeated adjustments.

Users want to be able to store dependencies / plugins from gradle files, but the file format is code (kotlin or groovy) It would be great to support parsing of these files for the file kind for the git providers

Now, the only way to assign permissions over an entity is by using owning_teams property and configuring the ownedByTeam: true/false on the blueprint permissions. We would like to define custom teams arrays as properties that can be inherited from relations and assigned granular permissions over entities (just like owning_teams, but being custom properties).

Number chart specifically, but any other widget that support selecting a specific entity should let you filter on the entity based on other properties other then identifier. Use case, you have a deployment blueprint with X entities, but you want to show in the dashboard only the latest deployment properties

Right now the Related Entities table shows all the related entities, not just directly related entities. It would be helpful to see how each entity in that table is related (whether it is direct, and if not how many degrees it is out). It would also be nice to have the option to default that table to just direct relations as well as offer the ability to filter by degrees of relation.