Feature ideas

Currently, the catalog filtering options allow for past time filtering, such as "in the past 365 days." It would be beneficial to extend this functionality to include future time filtering. For example, adding a filter like "in the next 365 days" would help us better to present catalog items relevant to future timeframes. In our case we want to have all the future on-call shifts for a user :)

No way to create an entity from the related entities section of a page. In many cases, where the user doesnt want a catalog page for the entity, there is no other way to create it, unless you're a builder. Also relevant when users want to link all related entities. Where there is no naming convention - people want to be able to stay on their service entity page and link all the relevant cloud resources, or whatever else. Going the other direction to find every cloud resource and map it to the service is more taxing because you have 2 searches per relationship, not 1, it's O(n^2) not O(n)

Users seem to really like being able to customize entity tables in any context, to create something specific and useful in different places. There are two places where I have discovered one cannot save a the reconfigured table (columns, filters) from the My Entities component on the homepage from the view entities button on a blueprint on in the data model view I'd say the former is bad for users. We shouldn't offer anything on the homepage that can't be tidied and saved I'd say the latter is bad for builders/power users, who delete catalog pages, but still want/need to browse entities for a blueprint from time to time https://us06web.zoom.us/clips/share/w9L4VxAPMVcmJdOJ_h5hoUS2MGYUS7RTve7xmKHwbMQqSL7v7v-UH1ClMqpYpXLzBnE9R32BhSRuM5jdiNbcpTSb.ZXP5FU-AMN-TT60m

When using the catalog page to view an entity, the back button takes you back to the last page in your browser window history, and not back to the entity catalog. This means that if you open an entity in a new tab it won't do anything, and if you paste the entity link in an existing tab it would take you back to the previous page you were on (that might be unrelated to Port). It would be nice if the back button would take you back to the catalog. Attaching a video demonstrating the current behavior.

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.

Today, in table views, the first column is a built-in entity logo column which cannot be removed or reordered. There are cases when we want to remove this column, e.g. we added a 'Link' column and would like to use the entity logo for it without having two columns looking the same, when only one is clickable which is both confusing to the user and takes up precious screen real estate from more important information. The built-in column should be treated as a normal column which will allow us to customize it like any other column.

Add an ability to view a column of row number in tables. This will help understand the ranking of ordered items. e.g. see the position of bug X in a bugs table ordered by priority score.

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.

It appears that table filters can only AND together all the filters or OR them together. It would be good to have the flexibility to use both at once.

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