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.

Create an MCP server exposing Port's capabilities to LLMs and AI agents. By entering this ecosystem, Port can become a tool developers meet in their tech stack (e.g., when coding in Cursor, ask questions like "when was the last successful build of this components", or give commands like "can you nudge my PR reviewers")

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

Enable users to validate integration setup before full installation by testing connectivity, access, and basic permissions. Reduce setup errors and improve user confidence in integration correctness during onboarding.

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

The ability to grep on git repo files via regex, so we can do campaigns on Java, sb3.x, terraform as they are files present in the repo. Today it's possible mostly using bringing the whole file and having a calculation property / using a script of your own.