Feature ideas

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

A common use case when building a developer portal with Port is changing the data model to fit new requirements (types, names, etc). This capability enables you to use JQ to calculate the value of a relation based on other blueprint properties.

Approvals are a bit limited. An approver cannot log into port and see his own approvals. Only Admins can see outstanding approval requests. The information to the approver is very limited- when they see the approval link, they need to view the json payload to see the details of what they are approving. Suggestion is that Approvals move to a blueprint model whereby all of the existing goodness, customisations and automations can be inherited to this workflow for free.

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.

Currently, you cannot delete any custom logos you've imported. It would be useful to have an API endpoint to remove unwanted custom logos. At least, uploading a logo with the same name as an existing logo should override it, so even without deletion, you can replace unwanted custom logos.

Sometimes customers have a complex data model with many blueprints and the default view has many overlapping blueprints and relations which can be confusing. Customers can move the blueprints around in the UI to make the data model look less chaotic, but they don't persist in the UI after you log out. Customers would like this to be the case so the view is less chaotic.

Extend markdown property support to handle non-UTF-8 encodings and invalid Unicode characters. Markdown content may originate from various sources and tools and is not always guaranteed to be clean UTF-8. Failing hard on a single invalid character makes markdown properties fragile and can block ingestion for otherwise valid entities.

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

I cannot create a calculated Timer Property. maybe it was forgotten to implement.

We are going about cataloguing a list of entities (type doesn't matter). These have to be manually discovered in our company and then we add a entity.json to the repo's so they get harvested and ingested into Port. Given the distributed nature of the repos this can take some time. We'd like to first "manually" register these entities in port and then over time sync them to their entity.json metadata as those are merged into various repos. You can see the source of a entity by looking at the audit log screen but I can't surface this on the catalogue table view. So I can't tell which ones are just manually still waiting to be linked to a entity.json etc. Could we have a new column that pulls the most recent audit log change for the entity source. So "API" etc or "Manual"