Feature ideas

Current behavior: only admins/editors can add filters; members can only adjust existing ones for their own view. Desired behavior: all members can create their own filters, scoped to themselves, without needing page edit rights. Why it matters: avoids “special orders” per user; “open source filtering” UX for members. Constraints: these filters should be personal to each member's view and not change the global view for others.

When resolving dynamic approvers, only the first 1,000 users in the organization are evaluated, Any users beyond that threshold are skipped, even if they match the required approval groups. Increasing this limit would be helpful.

We want to be able to filter a dashboard according to a timedate property so it will show only the last 3 days. The current predefined options are either use static dates, or choose between in the past day or in the past week. We want to be able to select the number of days in the past or in the future when relevant.

Currently, search conditions cannot be applied to calculated properties in self-service actions. Adding support for this is required

Support for multihop relationship that is both downstream and upstream from the base blueprint in the global dashboard filters For example: Application has a property relation to Service Service does not have a property relation to Application Deployment Frequency has a property relation to Service Therefore the flow is Deployment Frequency -> Service <- Application And we would like to filter the Deployment Frequency based on the Application, a sort of U shaped relationship (downstream to Service and then Upstream to Application)

Add support for breaking down by property in a pie chart for calculation properties, scorecards, and scorecard rules

Today, integrations only delete entities that were originally created by the exporter/data source. Entities created manually or via the API can be updated by integrations when discovered, but are not deleted when removed from the third-party system. It would be nice to have an optional toggle/flag to allow integrations to also delete these API-created entities.

Allow authentication using OIDC to Azure in the Azure Resource Graph Integration to allow for customers that leverage OIDC to connect to it.

Request to add support for time-bound approvals on self-service actions. If an approval is not completed within a configurable time window (for example, 7 days), the action run should automatically expire and be blocked from approval or fail safely. Request motivation: Late approvals can trigger actions that are no longer relevant and may cause unintended or harmful changes.

Currently there is no way to use org level variables or secrets in actions/automations. We would like to not have to hard code secret values into actions/automations fields when needed from the client side. As an admin it would be nice if there was a type of variable that could be set that could be used as a variable in any action or automation and if there was a way to easily change said variable.