Feature ideas

Current Behavior Any property or score (including rules) added to a blueprint automatically appears under all card widgets within that blueprint’s entity page views. Issue I have blueprints with entity page views containing multiple configured cards that group properties for different purposes. When a new score or property is added to an entity, all of those cards are instantly prefilled with the data. This results in unnecessary clutter and confusion across the cards. Suggestion Hide all properties by default, as was done under tables ( https://roadmap.getport.io/ideas/p/property-exclusion-in-tables ). Alternatively, allow the user to choose whether a new property or score should appear under widgets.

It would be nice to embed the markdown from an entities markdown property in a markdown widget. This would be very helpful on the new Entity Overview page.

Currently, when selecting the information ("i") icon and clicking the associated URL, the link opens in the same tab, navigating the user away from the Port environment. To improve usability, these links should open in a new tab or window, allowing users to reference the documentation without losing their place in Port.

In order to have an easier glance of related entities, it would be very helpful to have "filters" in "graph view" similar to how it's being done in table view. This way you can easily hide entities not just by blueprint (as currently available) but also by properties.

Ask questions, discuss, and make decisions within context. Allow developers to discuss and comment on different entities directly in Port.

I would like to have a widget which shows me property distribution using Heat map view

Currently, you can ingest markdown documents into Port by creating markdown properties. Each document will be displayed in Port as a tab on the specific entity page. We would like to add the ability to create a "documentation tree" for each entity, allowing you to create a full wiki inside your developer portal. Similar to the singular markdown documents, the documents in the "documentation tree" will be searchable via the global search .

Have the ability to hide specific fields in specific entity page which will not reflect to all entities in this blueprint

Allow the hidden properties which can be set for a blueprint / entity in the ui to be configured via the terraform and pulumi IaC providers

Currently Terraform has only partial page management, with the ability to edit basic pages such as dashboard and blueprint-table; but it has no support yet for specific entity pages.