Feature ideas

Currently we can provide a URL pointing to a tab that shows the rendered spec for swagger/openapi files but we cannot link to specific endpoints inside it. This would help our backend & frontend teams better coordinate together when working on features.

When querying the Audit Log API for entity updates, the actor is returned as a userId. There’s no direct way to resolve that ID to a name/email. Today we must fetch all users in the org and filter those results client-side. Please add a direct resolution path (such as GET /v1/users/{userId} or GET /v1/users?ids=<id,...>) or allow filtering the Users API by id.

Context https://docs.getport.io/search-and-query/#relation-structure-and-operators describes how to search for Entities that have a relation to other Entities. This can be used with the search API ( https://api.getport.io/v1/entities/search ) and with the filters when adding a visualization to a dashboard for example. This type of search only has one operator: relatedTo . Objective Add an opposite operator, i.e. relatesNotTo . Rationale Sometimes the business context dictates that certain relationships SHOULD be present in the data. By adding this operator it becomes possible to find inconsistencies in the data by searching for Entities that do NOT have a relationship (where one is expected).

There are some blueprints that I always want to exclude from global search (e.g. releases). When they are included, it ruins the search results. I want to be able to configure it globally, i dont want to have to add a search expression to the global search

I would love to use icons for the sidebar folders for better visibility

It would be useful if https://api.port.io/v1/migrations supported search queries with relations like the ones below. { "combinator": "and", "rules": [ { "property": "$blueprint", "operator": "=", "value": "service" }, { "relation": "artifact", "operator": "=", "value": "{{ . event.diff.after.properties .artifact }}" } ] } or { "combinator": "and", "rules": [ { "property": "$blueprint", "operator": "=", "value": "service" }, { "operator": "relatedTo", "blueprint": "artifact", "value": "{{ . event.diff.after.properties .artifact}}" } ] }

When a search relation returns a large number of related entities (e.g., 300+ Functionalities for a Product), it leads to performance degradation or failure. This limits usability in high-volume use cases. The request is to improve search relation handling to support large datasets efficiently

Today you can only use relatedTo to check if an entity is connected to a certain entity on a related blueprint. When using Port I'd want also to check the entities that are not connected at all to any entity in the related blueprint. For example - All Workloads that are null in the "Namespace" relation

Currently, global search results are based solely on the keyword(s) entered. For organizations with many entities, it would be helpful to do a few things with global search, such as: filtering (provide filters to the search using a search dropdown for blueprint, properties, relatedTo, etc), semantic search, and adding filters within the search query (such as in:<blueprint>, <search query A> AND <search query B>, NOT <blueprint>)

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.