Feature ideas

Today, when updating new objects / arrays of entities the new value overrides the old one. With this feature it will be possible to append values to these properties. Example of Tags property with type of array: Current state: "Tags" : ["tag1"] Ingesting a new tag using the API: "tag2" New state: "Tags": ["tag1", "tag2"]

We want to be able to pull all the closed PRs from Jan 1 2025 and not just from X days ago as it is not possible in the github ocean integration.

The Integration Event Logs page is difficult to use when there are many logs. It currently uses infinite scroll, so logs only load while scrolling. This makes troubleshooting hard and makes it easy to lose the selection when trying to copy multiple log lines. In addition: The in-page search does not jump to the matching log entry There is no option to download logs There is no date/time range filter in the UI Users have to rely on the API for proper filtering Requested improvements Add pagination (or allow pagination instead of infinite scroll) Add a Download logs button to export filtered logs Add a date/time range filter in the UI Improve the in-page search so it navigates to matching log entries These changes would make the logs page much easier to use for troubleshooting, especially when working with large integrations that generate a high volume of logs.

Currently, any change to your integration mapping requires a full resync - re-fetching all data from the third-party API- even for minor adjustments. This can be slow and creates unnecessary API load. With this feature, you'll be able to apply mapping changes instantly using the data already stored in Port, without triggering a new sync from the third party. This means faster iteration on your mappings, fewer API calls, and quicker time to see your changes reflected in the portal. Full resync remains available whenever you need fresh data from the source.

Add support for the Jira Ocean integration to authenticate using a Jira service account's credentials (e.g., API token or PAT), without requiring that user to have access to Port or an admin role.

Allow the {{ .secrets.<secret_name> }} syntax in the secret field for webhook, consistent with how secrets are already used in self-service action and automation payloads. Example "security": { "secret": "{{ .secrets.github_metrics_integration_secret }}", "signatureHeaderName": "X-Port-Signature", "signaturePrefix": "sha256=", "signatureAlgorithm": "sha256" }

Introduce a way to trigger alerts when a data source sync fails, allowing teams to integrate Port with their monitoring/observability stack. This could be achieved via automation trigger (add a trigger for “sync failed” events scoped per exporter and/or per kind). Or, via a built-in alert configuration (add an alert configuration section within the Sync Status page, and allow users to define notification rules for failed syncs).

Problem The Event Log is difficult to use for troubleshooting: No severity filtering in the UI (only available via API) No way to navigate from a step directly to its logs Partial failures are not visually distinguished from full success Log history capped at 1,000 entries with limited search Requested Improvements Severity filtering in the UI, filter by INFO, WARNING, ERROR, etc., with the option to suppress noisy info logs Step-level log navigation: click a step to jump directly to its logs Partial success indicator: visually distinguish partial success from full success/failure Download logs: export logs for local searching Timeframe selection: filter logs by time range

Port should compute current vulnerabilities from only the latest completed scan per project + branch + scan type, not from all scans in the time window. Problem: When multiple historical scans are processed, vulnerabilities fixed in newer scans can still appear from older scans, creating stale entities. Proposal: Group scans by project + branch + scan type. Select the latest completed scan in each group. Sync findings from that scan only. Optionally delete findings missing vs previous latest scan in the same group. With this, More accurate current-state vulnerability data and fewer stale findings in Port.

When visiting a specific page in Port I would like to automatically trigger the (re)sync of a specific data source. Currently my option is to manually resync it from the Builder page, or start a Self service action to trigger it.