Feature ideas

Developers/users can have community discussions or QA boards like Stack overflow in port

Currently if the table query gets broken due to syntax errors in the initials filters the table shows its empty state. This is confusing as you might think the filter is correct but not qorking as expected. If I would see the query error somewhere I could easily identify the issue without the help of the support engineers. Same for the query filters.

For security use cases, integration with Blackduck for retrieving vulnerabilities, issues, etc

It would be great to have an option to do bulk actions(day2 and DELETE) on entities

Currently, admins who add secrets are not able to see the value of the secret they're adding. In cases where they use this secret and get an unauthorized error, it would be helpful to see the text they are entering to ensure it is 100% correct.

In the URL property type settings if there could be a setting to select to change the behavior of clicking the link, either it opens in a new tab or not, or even in a new window, this would help admins curate an optimal user experience.

When a user executes an action and isn't supposed to (for example entity is created already), the message they get is "contact your admin". It would be good for admins to have the option to predefine a set of message when each rule fails

Dashboards allow adding number charts, but lack the option to customize their color. Adding a color selection for each number chart would help convey different meanings based on context (e.g., red for critical values, green for successful outcomes). This would improve data visualization clarity and the overall user experience. Benefits: Clear visual distinction between metrics. More customizable and visually appealing dashboards.

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")

Currently, validation prevents me from creating two dashboards/pages with the same name. However, this is a perfectly valid need for customers, who may want different personas to each have a "scorecard", "plan my day" or their own matching initiative dashboard page Even a UI option to create a new page as JSON would allow the differentiation of ids