Feature ideas

Currently it is not obvious for users that they have to type in their email in the login box to use SSO.

Currently, the Data source will only display cubicles of Blueprints that were successfully ingested through that data source. Having feedback about failed ingestions (for example, display the blueprint with red background) could help understand if the issue is related to mapping config syntax.

Currently, the "entity JSON example" section in the JQ playground is automatically filled with dummy data according to each property type. We would like to provide in that section the option to get real data from the catalog in addition to the dummy data option. In addition, we will add support for "YAML" property to convert YAML data into JSON to be used in the JQ calculation.

Right now, I have the port icon and name for all my open tabs for Port, It will be great if more information will be displayed their, for example the catalog I'm on like AWS does with it's services.

Working with Port’s JSON editors is now a piece of cake! from now, automated text completion will help you see and choose the available values for each property directly in the JSON editor. The feature can also be activated manually with a keyboard shortcut: Mac - alt+escape Windows - control+space

The GitHub & BitBucket integration configuration is now editable via Port’s UI. This capability is available in the “Git providers” and “GitOps” categories. You can view & edit the configuration by going to a blueprint’s three dots menu → “Ingest data” button → clicking on one of the GitHub/Bitbucket integrations.

The main navigation (catalog, self-service, and builder) is now at the top section of the screen, and there is a new "Catalog" section with a side menu containing all catalog pages. The new side menu can be resized!