Feature ideas

It would be useful to show data from multiple blueprints in a single chart based on property with the same name or based on number of entities per each blueprint. An example is: we have blueprints for Car and Plane entities with properties (along with other properties) called "number of passangers" and "owner". Then we would like to visualize number of cars and planes in a single pie chart with "breakdown by property" set to owner or "number of passangers". This chart would then show us how many means of transport each owner owns.

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.

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

Additional filters of widgets allow to set only one combinator. Example: { "combinator": "and", "rules": [ { "property": "argocdAppName", "operator": "contains", "value": "staging3" }, { "operator": "=", "value": "argocdApplication", "property": "$blueprint" } ] } it would be good to have the ability to write more complex conditions. combine AND and OR combinators

Add the option to add a currency sign to the numerical field automatically (maybe via a separate currency property) Allow formatting long financial numbers for readibility (e.g. similar how Excel does it)

The ability to conditionally highlight a table row would be a very useful UX ability. Imagine something with a failed property being a red row. Or the latest 3 entities being highlighted in green.

Currently, when an entity has a URL property, hovering over it displays the full URL, which can sometimes be confusing. What if we showed an alias instead when hovering over the icon of the URL property? This way, it would be easier to understand each icon’s purpose at a glance.

Currently, filtering Datetime properties is limited to either relative (last x days) or a time range (05/01 - 07/01). Being able to filter data such as "is not null" "specific day of the week(i.e only tuesday)" and more, can provide some nice information. For example, create filter for all environments were the last login date is "null" indicating that they were never logged in to.

For example using a calculation property in initial or additional filters or performing calculations on a calculation property. Port should provide a warning or error message indicating that a specific action or feature is not supported

When using Pie Charts, you cannot use the breakdown by a related entity, which requires us to map a mirror property for $title to do it. However, you can group by related entities in a table, meaning that we don't need the mirror property for it in this case. Extra mirror properties are duplicates then depending on the use case and cause more maintenance and initial configuration.