Feature ideas

The capability (descriptions for rules) should be added to the provider, as it's missing in Pulumi providers

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.

This new approach will create scorecard blueprints and entities (Scorecard, Rule, and Rule Result) in real-time and will allow you many experiences that were missing up until now, such as: Scorecard and rules management board with the ability to enrich metadata with categories, SLAs, due-dates, and owners Setting automation and actions like "Ask for SLA exception Create custom widgets like view all failing rule results related to entities owned by me or management view on rules passed Utilize aggregation properties and line charts to track initiative progress And anything else you can do with Port!

Using the Port sender GitHub action, you can sync your scorecard rule results and create/resolve Github issues accordingly. This feature request talks about the ability to load custom GitHub issue templates for the created issues.

Today scorecards are created by editing a json. The idea is a UI that will show the user all the possible operators, and build rules easily for a new scorecard.

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

"filter": { "combinator": "and", "conditions": [ { "relation": "repository", "operator": "=", "value": "bananas" } ] }, Above would apply to the whole scorecard as it’s not a possible field on each rule. If we have a service blueprint and want an entity to be ignored by certain rules of a scorecard, we should be able to filter on each rule. A scorecard will have multiple rules, 7/10 may apply, the other 3 we can use a common property to ignore and ‘pass’ the scorecard but that is irrelevant information to the entity and it fakes a pass when it should be ignored, just like the filter above does for a whole scorecard. E.g. if I have an observability scorecard and it has 10 rules which are datadog monitors, datadog alerts, sentry alerts etc etc ..but some entities (lets say 5/40) can ignore this, I want to ignore them cleanly by using a filter. https://port-community.slack.com/archives/C07CB3MV63G/p1726578072124179

We would like to be able to link, to a blueprint, a (complexe) assessment form that the developers could answer. Our usage is to help assess the maturity of the tech assets regarding our Enterprise engineering practices. So we need to enter assessments regularly and calculate some scores based on the answers. This score should be historized and independent of the questions modifications (as the requested maturity and questions can evolve from year to year).

Lets say I have a property of type enum that provide the types of CVEs currently found for a service. the enum values are CRITICAL, HIGH, MEDIUM, LOW. The "CVE levels" property could have those values : MEDIUM, LOW, meaning there are no CVE of type high or critical (for now :) ). What would be great is to be able to compute a score card tier according to the type values. We could show bronze, silver or gold depending on the values in the property.

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.