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.

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

Ensure the side panel automatically scrolls to bring the highlighted item into view when navigating via URL or link.

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.

It is necessary to have subdomains, for example, https://latam.getport.io and https://latam.env.getport.io , to allow customization and avoid issues when working in different environments. Currently, we are experiencing issues with redirection between environments, where users are being redirected to the development environment when they want to access the production environment.

This is example for query: { "combinator": "and", "rules": [ { "property": "$blueprint", "operator": "=", "value": "myBlueprint" }, { "property": "$identifier", "operator": "contains", "value": "myIdentifierPart" } ] } Unfortunately, there is no option to limit the results. Please consider adding a limit and offset mechanism.

The endpoint https://api.getport.io/v1/entities/search does not allow to search in a JSON object and contains does not work either.

I would like to be able to navigate port using a keyboard, with a set of keyboard shortcuts

Whether in the global search, or searching within a table, I'd like to search using regular expressions to take advantage of known conventions or shapes to the data (e.g. starts with, optional characters, etc)