Feature ideas

Current behavior: Once the table is grouped by criteria, all scores/enums receive a quantity visualization of proceeding values under the group. However, for numeric properties, nothing is displayed. Suggestion: For grouped numeric properties, reuse this empty space to provide a user-selected metric (e.g., average, median, etc.).

Current behavior Numeric values are displayed as plain text below the table. When a table contains many numbers (across both entities and properties), it becomes hard to identify the “problematic” value that needs closer inspection. Proposed solution While scorecards can achieve a similar effect, it’s also helpful to see which specific value drives a score up or down. I suggest adding an additional property to numeric fields that lets us declare a color indicator. This would visually highlight values that require attention and make it easier to spot outliers directly in the table.

Additional Filters, Builders, Blueprints contain JSON and YAML. The inputs tend to show the data in a way that it is hard to read by a human. Either a way to prettify or to render prettified data by default would be the goal.

I would like to be able to create more granular filters in regards to date time filters. For example: Entities created since last Tuesday (Dynamically) This can help solve all sorts of usecases such as showing incidents in regards to a specific on-call week etc.

Correctly, If needed to display a chart in time frame X you will need to create a widget for each timeframe - not so user friendly Please add an option to choose the timeframe from a drop down this way users will be able to filter the data according to their choice and will remove duplication of widgets that shows the same data only in different timeframe

Letting you add any icon you want into the organization's private icons library

Would be very useful to have the ability to select multiple entities on the page and bulk delete them all

I tried this: { "value": [ "library", "other", "micro-frontend" ], "operator": "doesNotContains", "property": "type" } In hopes that I can filter out types I don't want. But apparently doesNotContains does not support arrays and have to write 3 != rules instead Would be helpful to allow arrays

Currently, table views are based on polling data from the API, and in order to view a change immediately you will need to refresh the page. Implementing Server Sockets will allow changes in data to be reflected in real-time instead of refreshing/waiting for the interval.