Feature ideas

Improve UX of Searching in Port by referring to 'Filter Option' to check if matches the criteria. Currently, most users are not aware of default filtering exists, therefore when they search for entities outside the filter set they get an empty result. To improve the user experience, it would be best if Port can highlight/refer users to 'Check Filter Option to make sure if needs to change to fit their search". This can have a significant impact on the UX.

Allow users to build their own interface components as widgets, with Port's catalog context at hand.

Provide Monitoring and Sync Status details, which are currently provided for all the Ocean integrations for k8s-exporter and port-agent as well.

To address brand logo requirements (i.e. min width 48px, no borders, no rounded corners), custom theming functionality in Organization Settings should be expanded. Current limitations: max-width - 34px border border-radius (rounded corners) 1 image for both themes (light and dark) Suggestions: Add 1 more link for dark theme icon Add input for icon size Remove border and radius, or add checkboxes / toggles to add/remove border and radius

As a FinOps team member, I want to ingest data from FinOut to deliver it to developers. Right now, I struggle to deliver FinOps optimization advice to them and doing so in Port is the ideal way.

Currently when you set the blueprint identifier for a Day-2 Self-Service action, its entity is placed automatically at the top of the form inputs without the option to control its order. There could be scenarios in which the selection list of the target entity is too large and it gets complicated for the user to figure out what instance to choose. This is a limitation that prevents you from having input filters placed before the form's target entity that will help you narrow down the options for the selection list of the target entity. Example: You have 3 entities A, B and C. The relations goes like this C -> B -> A. If I have a Day-2 Action that takes action on the entity C, I want to be able to include the A and B entities in the form and be able to select them first (for filter purposes) before choosing directly between the instances of C, because unfiltered, there could be a lot of C instances to choose from, and it gets hard to identify the exact instance that you need only by checking its name (not knowing the relation to A and B).

Currently Ocean exposes Prometheus metrics at /metrics/. This feature request tracks adding an out-of-the-box ServiceMonitor manifest to the Ocean deployment (with appropriate labels, namespace, and endpoint configuration) so users can enable metrics scraping immediately without extra work.

Today we have a static and strict small schema we bring about users and teams when integrating with an identity provider (user names, mails, team names) The idea here is to have the whole payload coming from the SSO provider (the schema should be known based on the SSO protocol) and for Port builders to be able to decide what they want to map to the user and team blueprints.

The markdown widget supports the use of svg tag, but not inner tags like path, line, and rect. These tags should be allowed in order for the svg image to be able to render.

On a lot of entity pages we have a lot of data to display. It would be nice to be able to group widgets in clickable labeled drop downs so that users don't have to scroll past a large amount of widgets not relevant to what they're looking for.