Feature ideas

Adding Tabs to dashboards would allow for logical organization that would avoid needing to create multiple dashboards or one long complex dashboard. Example: a dashboard for Deployments where there is a tab per Environment.

Currently, you can ingest markdown documents into Port by creating markdown properties. Each document will be displayed in Port as a tab on the specific entity page. We would like to add the ability to create a "documentation tree" for each entity, allowing you to create a full wiki inside your developer portal. Similar to the singular markdown documents, the documents in the "documentation tree" will be searchable via the global search .

Currently, there is no way to offer input selection based on API. Implementing this could allow forms for specific services based on their API responses. For example, create a dropdown selection of Github organizations based on an API call.

Dear Port Development Team, I am writing to formally request an enhancement to Port’s AWS resource monitoring functionality, specifically to include AWS resource creation timestamps during the Ocean Exporter data injection process. Currently, the Ocean Exporter collects and injects AWS resource data into Port daily but does not capture creation timestamps. This limitation poses challenges in: Tracking the exact timing of infrastructure modifications, Maintaining accurate audit trails, Correlating operational events with resource changes. Please feel free to reach out if you require further technical details. Thank you for your attention, and I look forward to your response. Best regards

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.

I think it will be great if we will have on the dashboard page of entities the ability to change the location of the widgets in the dashboard and the widget's size. In addition, to have the option to present only the dashboards which have data

Today manual approval can only be configured as a gate to prevent an action from starting. In some real-life workflows, an action might perform some process and then arrive at another point that requires manual approval. Port should support such cases by making it possible to update the state of a running action, allowing it to require approval again (maybe even from different approvers) and only then continue its work, probably by sending an approve request to the pipeline system that is currently stuck

Add a confirmation window in the GUI mode in Self-service action window to prompt users when they attempt to navigate away from the page without saving their changes. Currently, this confirmation prompt exists in JSON mode in Self-service action window, but it is missing in GUI mode, which can lead to accidental data loss. Rationale: In the GUI mode, users may accidentally navigate away without saving their changes. A confirmation prompt will help prevent this, ensuring users have the chance to save their work before leaving the page. This feature is especially helpful for complex edits where re-entering data can be time-consuming. Expected Behavior: • Trigger: When a user tries to navigate away from the page while unsaved changes are present in GUI mode. • Confirmation Prompt: The prompt should ask the user, “Are you sure you want to leave this page without saving changes?” with options to “Stay on Page” or “Leave without Saving.” • Consistency: This behavior should be consistent with the existing confirmation prompt in JSON mode to ensure a seamless user experience across modes.

We use https://www.anodot.com/ for FinOps and would like to have its integration with Getport.

Having a built-in feature to sync Port’s service catalog directly with incident.io would be beneficial, as it would help in removing the dependency on external CI/CD pipelines.