Feature ideas

It is often the case that there are sets of properties applicable to many blueprints. For example, documentation related URL properties could be created and attached to each blueprint without a need to copy-paste them. This capability is known as a Mixin (see https://en.wikipedia.org/wiki/Mixin ). A Mixin nicely complements inheritance, since there is no need for an additional data type just to enable reuse of implementation. In other words, thankfully to mixins we could eschew implementation inheritance, which on long run usually causes maintenance problems. For an idea talking about inheritance see https://roadmap.getport.io/ideas/p/native-inheritance-in-blueprints

The IaC options currently do not allow for management of READ permissions on entities (all other permissions for blueprints appear present). In our use case, we would like to deny READ permission access to the private feedback we will have our teams submit using a self-service action. Unfortunately, we cannot roll this change out through IaC, it is going to have to be done manually in the UI. Its awkard and will certainly bite us in the future not to have READ permissions source controlled with the rest of the permissions.

Add pagination to the Port API.

Manage your users and teams the same way as all your blueprints! This will enable you to: Add additional properties to teams and users Create relations between user, team, and any other blueprint See teams and users as part of your relations graph

We have multiple different types of component . Currently we either need to model them as entirely separate blueprints or we try to merge them into one common shared blueprint. The latter has proven to be a bit unwieldy, when differences arise between types they tend to bleed through in the Port UI in certain places making the UX for the user a bit confusing.

One of our data sources has IDs of type "UUID". Of course I could store them as a String, but being able to store them as a UUID (which would be a numeric value rather than a String) could be more efficient in terms of storage, filtering, sorting, linking, and so on.

Sometimes a property should be set at creation time and never changed again. There should be the ability to classify a property as immutable so that the value is guaranteed to always be the same.

Having the ability to choose the order of the enum values, other than the default A-Z.

Centralized application for the community to share their data model and use other customers data model design (With the ability to import blueprints design to your Port environment)

When you want to present job duration, a time delta property will be great addition. It can be presented as 1min or 1:23h depends on the size.