Feature ideas

I have an entity with a markdown field for ingested documentation, and I wanted to build a scorecard rule with some basic tests on that documentation (is it non-empty, does it contain a link to Port, does it contain a badge, etc.). However, none of my markdown fields appear in the scorecard rule condition property list. Please allow markdown fields to be tested like string fields in scorecard rules.

When a new integration is successfully connected and finishes its initial sync, Port should automatically generate relevant scorecards for the onboarded entities. Today, integrations populate the catalog and users can explore entities via catalog pages. However, there is no immediate, opinionated layer that translates the ingested data into actionable insights. Customers are required to manually define scorecards after setup, which delays time-to-value. Automatically generating baseline scorecards would create immediate, consumable insights beyond the catalog UI.

Currently scorecard rules are defined by conditions that use the search/query system but these can get complicated for complex rules. It would be very useful if you could directly use JQ in these conditions.

Currently, Scorecard rules can only be compared to a fixed value. Adding the option to compare between properties of the same entity, will allow more dynamic scorecards and cover more use-cases.

To be able to track scorecard result overtime, to be able to aggregate on a related blueprint (how many Gold in this environment for example). Today we see the scorecard result in a table, but we are unable to represent it in a line chart or to aggregate on it or mirror it

There are cases where the scorecard is governed by same property and different rule condition, this appears to be cluttered on the UI, requesting a toggle button or the feature in json for scorecard to enable/disable of having rule displayed on the catalog page for that particular entity.

A dedicated page for all scorecards and rules defined in the organization

Requesting a feature to enable mirroring scorecards created for one entity onto the scorecard of another entity. Use case: For example, an AWS Resource entity has scorecards, and the entity is related to a Service entity that maintains a catalog of all AWS resources under that service. This would allow further grouping of scorecards for creating initiatives or achieving better organization. This functionality is currently not supported.

We'd like for developers to be able to define arbitrary thresholds for scorecard “badges” colors, so they could get their color dynamically changed based on the value they hold. For example, when the number of vulnerabilities is rising, the color would swap to “scarier” options (green -> red). Users might have different reasons and conditions for color-coding their scorecards, and leaving the threshold setup up to the customizers might be easier.