Feature ideas

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.

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.

As a Port builder, I want to apply weights to scorecard rules. For example, if my rules are has a README has a team had an outage within the past week I would want to weigh the third rule more heavily than the previous two. The total number of rules passed above is 67%, but if I were able to add the following example weights to the rules, the overall score or grade would be 50% has a README (25% weight): 25/25 has a team (25% weight): 25/25 had an outage in the last week (50% weight): 0/50

The scoreboard order keeps on changing even if we arrange in the json.. or in other words there is no way to order the scorecards in the way we want.

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

Currently, we are limited to 20 characters for scorecard and scorecard rules titles and identifiers. This is quite limiting for us, especially for titles as we have to sacrifice readability. A limit of 50 characters or more would be more acceptable for us.

Port Sender Github action can send scorecard notifications using slack_webhook_url associated with a specific channel. Requesting support for providing channel-id as input for github action to slack messages with same slack_webhook_url. Port Sender Github Action - https://github.com/port-labs/port-sender/tree/main https://github.com/port-labs/port-sender/blob/main/targets/slack.py#L4 Currently, it is using WebhookClient which allows posting messages using slack_webhook_url associated with specific channel - https://tools.slack.dev/python-slack-sdk/webhook Suggestion to implement WebClient, which will allow channel-id as input parameter for posting slack messages - https://tools.slack.dev/python-slack-sdk/web references : https://github.com/port-labs/port-sender/tree/main https://github.com/port-labs/port-sender/blob/main/targets/slack.py#L4 https://tools.slack.dev/python-slack-sdk/web https://tools.slack.dev/python-slack-sdk/webhook

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.

I want to build a scorecard rule that restricts available choices like an enum. For example, ensure that I have a component type defined that can only be one of "service", "application", "tool" or "documentation" but nothing else. These operators are already available in the search endpoints: https://docs.port.io/search-and-query/comparison-operators#in and https://docs.port.io/search-and-query/comparison-operators#notin