Feature ideas

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@_.+:\\/=-]+$"

Some data models include blueprints such as CI/CD jobs or deployments. These blueprints usually get filled with high number of entities, but the entities in these blueprints become stale and lose relevancy very quickly. With this feature, users will be able to configure custom retention for specific blueprints, giving them the option to automatically delete old entities once the number of entities for the blueprint passes X entities, or if an entity was updated more than 1 week/month/year ago

The ability to look back it the graph and take the latest entity that was related to my entity. Examples: Deployment -> Service In the service we will have the "Latest Deployment" agg property Pull request -> Service Latest merged pull request Image -> Service Latest image User -> Team Newest team member

Currently aggregation properties are only being calculated on number properties and not date properties.

Similar to the request for Gradle files, it would be valuable to parse go.mod files for dependencies and making scorecards for that.

I would like to propose adding the Semantic Versioning property type to the blueprints. This change will enable the possibility of ingesting data like the library dependency version properly. It should also allow the scorecard of this information to not treat it as a string. Example. 8.1.2 is greater than 8.0.1 Scenario I have a Service blueprint the blueprint has the node_js_version property the property type is semver I created a scorecard with the name LTS Version the current node js LTS version is 20.10.0 the scorecard should fail on version X.Y.Z where X <=20 & Y < 10 Source: https://semver.org/

Enable condition rules using property paths (e.g., related entities) to support contextual queries. This functionality is currently unsupported and requires a workaround using mirror properties.

Add the ability to mirror a property from a related blueprint even, regardless of the direction of the relation.

Add lead time for work items as part of the default blueprint and mappings

For instance i want to delete and try to create again some datasource. Now, i have to go to the datasource in json format copy schema to some place, re-create datasource and put this config again. Maybe, it will be super, if we have a button, create backup of all datasources in one time.