Feature ideas

Creating custom tiers for scorecards, without the limitation of the only existing 3 , and adding a custom color / icon to each one

Scorecards contain the list of requirements (rules) to reach the standard level desired defined by the organization in the different categories such as quality, production readiness, and more. Often, the developers need to perform different code and configuration changes to reach these standards. To manage these tasks, organizations will use their product management tool such as Jira. We will allow organizations to manage an integration with Jira to automatically open tasks for fixing specific scorecards and closing them upon scorecard changes.

A centralized dashboard for all scorecards that are managed in the organization. The new dashboard will contain a birds-eye view of all scorecards' progress, with the ability to drill down to each scorecard's status grouped by rules, teams, and more.

When grouping by scorecards in the software catalog, it can help to present the reason every entry is applied with the certain tier (tooltip/label that mentions the reason)

When defining scorecards, it would be helpful to be able to create rules that check if an entity has been defined in the relation. It would also be really helpful to either be able to create scorecards that refer to properties on related entities or to have scorecards that aggregate scores from score cards on related entities. I have two real world use cases to provide examples for this. I have the following entities with relations: Repository -> Component -> Resource The repositories are ingested from GitHub, so the component is not automatically populated. I would like to create a Scorecard that checks if at least one component has been associated with the GitHub repository. Similarly, a component may have multiple resources related to it. These could be external services, S3 buckets, databases, etc. I would like to be able to create a Scorecard on the Component entity that filters for resources that have the type 'Database' and check that the database technology property is set to one of a few organization preferred database technologies.

Filters for scorecards allow you to decide which entities you would like to evaluate as part of a scorecard. For example, set a “Production readiness” scorecard to be applied only for services that are not defined as “Experimental”. See how to define a scorecard filter .

When defining scorecard rules, you can use the new "description" property to further explain details about the rule, such as the importance of a rule and the motivation behind it. Descriptions can be added in markdown to add additional formatting, links, and more. Read more about scorecards here .