Feature ideas

In the URL property type settings if there could be a setting to select to change the behavior of clicking the link, either it opens in a new tab or not, or even in a new window, this would help admins curate an optimal user experience.

Users want to be able to store dependencies / plugins from gradle files, but the file format is code (kotlin or groovy) It would be great to support parsing of these files for the file kind for the git providers

Add format values e.g. currency, percentage, rounded, 1dp to a number property in a blueprint for when it is displayed either on the specific entity page or in a table Would stop having to define calc properties to get common number formatting options - simplify blueprints and improve display

It is valid for a user to have an apostrophe in their email address. Email address seems to be the defacto value used as an identifier for the system-managed _user blueprint. Example: j.o'bloggs@ourdomain.com Port does not appear to support such an email address. If we attempt to create such a user via the web app: > j.o' bloggs@ourdomain.com is not a valid email If we attempt to upsert the entity via the Port APIs, the audit log shows an error: > "identifier" must match pattern "^[A-Za-z0-9@_.+:\\/=-]+$"

Today a relation can be only for one blueprint, but this FR suggests having a relation that is modeled to be one of multiple blueprints. For example - "Resource" blueprint can be connected to one of - service, cloud resource, or on-prem resource, so we create this special relation, and for each entity the relation can be one of the connected blueprints. For mirror properties, you will be able to mirror only the common properties (meta properties, and intersecting ones)

I have to open a new tab, go to the data model, edit the blueprint and view as JSON, then scroll, just to check the exact spelling of an identifier property. Instead, I would like for these to be displayed or suggested when I need to reference them - e.g. in mapping, in json editor

Here I am generating “resource_prefix” from the previous inputs of “.properties.project_id” and “.properties.env”: "resource_prefix": { "icon": "DefaultProperty", "type": "string", "title": "Resource name prefix (auto-generated)", "description": "Resource prefix based on project and environment.", "default": { "jqQuery": ". form.project.properties .project_id + \"-\" + . form.environment.properties .env" }, "dependsOn": [ "project", "environment" ] }, This works very well. As for potential improvement I would like “resource_prefix” to be auto-generated from the previous inputs and NOT EDITABLE from the user form.

Currently when creating a new property, there is a 30 character limit for identifier and title. Increase in the limit would be helpful.

I would like to have the ability to use dynamic filters in the aggregation property. For example, I would like to filter entities that have a direct link to the current entity.

Currently, there is no option to add a mirrored property when the dependent blueprint property is a calculated item. Example: I have a blueprint with a URL-calculated property to display a Grafana dashboard. It would be beneficial if we could include this dashboard URL as a mirrored property for another blueprint that depends on it.