Feature ideas

Add support for reliably identifying the earliest commit & timestamp that belongs to a pull request across GitHub, GitLab, and Azure DevOps, as this is required to calculate Lead Time for Changes regarding DORA metrics.

Currently, permission changes made through Terraform are not captured in the audit logs The request is to add support for logging permission changes triggered via Terraform in the audit logs

Currently, Port's global search only indexes markdown content that is stored as a markdown-type property on a catalog entity (surfaced under the "Tech Docs" search category). Markdown content entered directly into a Markdown widget on a dashboard (using the "Custom" data source) is not tied to any entity and is therefore not indexed or searchable. This is a limitation for teams building customer-facing or internal knowledge bases directly within Port using dashboard markdown widgets. Users expect that articles and documentation written in markdown widgets would be discoverable through the global search, just like entity-bound markdown content.This is a limitation for teams building customer-facing or internal knowledge bases directly within Port using dashboard markdown widgets. Users expect that articles and documentation written in markdown widgets would be discoverable through the global search, just like entity-bound markdown content.

Request to implement consistent guardrail enforcement when triggering self-service actions via the MCP, so that dataset filters and advanced input logic are respected regardless of the execution surface (UI or API/MCP). Currently, the Port MCP bypasses frontend-only input validations (like dataset filters) when self service actions are triggered, allowing LLMs to select any value, which can violate intended permissions/guardrails.

Expose branch-level data from the GitLab API so Port can ingest it as service catalog properties. Specific fields needed: Last commit date (the customer currently has last activity date as a workaround, but wants actual last commit on the default branch) Last commit author (the person who authored the commit, not a bot/merge service account)

We would like to have additional GitHub Metrics come natively from the GItHub integration, for example the ones from this repo https://github.com/port-experimental/super-github-metrics

Currently, the maximum number of entities returned by a search query rule when mapping relations is limited to 500. There is no built-in way to exceed this limit. Since 500 may be too low for certain use cases, it would be helpful to provide an option to increase this limit.

Add support for reliably identifying the earliest commit & timestamp that belongs to a "Deployment" across GitHub, GitLab, and Azure DevOps, as this is required to calculate Lead Time for Changes regarding DORA metrics.

As we scale our platform and create more self-service actions, the current UI has turned into an endless scrolling page. It is becoming difficult for developers to quickly find the actions they need. Add a left-hand sidebar menu to the Self-Service hub that allows us to organize actions into nested folders and subcategories, exactly like the layout on the Catalog page. Example Structure: * Create Actions (e.g., Cloud Resources, Dev Services) * Day-2 (e.g., Scaling, Updates) * Delete Actions * AI Agents This will eliminate the endless scrolling, significantly improve navigation, and create a consistent user experience between the Catalog and Self-Service hubs. I've attached a mockup screenshot of how this could look!

Today, when updating new objects / arrays of entities the new value overrides the old one. With this feature it will be possible to append values to these properties. Example of Tags property with type of array: Current state: "Tags" : ["tag1"] Ingesting a new tag using the API: "tag2" New state: "Tags": ["tag1", "tag2"]