Feature ideas

The following resource kinds are not supported by the out-of-the-box Linear Ocean integration. Each gap blocks a specific use case in Port: User — Without this, issues cannot be contextualized for the logged-in user. "Plan My Day" and any person-centric dashboard are blocked. Project — Without this, feature-level progress tracking is not possible in Port. Cycle — Without this, sprint-level context is missing. Teams using weekly cycles (e.g. Platform team) have no visibility into current/upcoming sprints. Initiative — Without this, the roadmap/OKR layer is not visible in Port. Team membership gap (related): The team kind currently does not include team.members, even though team.members is available in the Linear GraphQL API. Without team membership data, it is not possible to contextualize issues for a logged-in user based on their team(s) — even if the User kind were added. Additional request: Out-of-the-box support for multiple Linear workspaces under a single integration instance.

We would like the ServiceNow integration's live-events (real-time webhook) capability extended to support any table configured for ingestion, rather than being limited to the fixed set of tables currently hardcoded in the integration documentation.

We are looking to sync ServiceNow incidents and requests near-real-time via ServiceNow Business Rules that POST outbound webhooks to Port Ocean's webhook event listener on record create/update. Port's ServiceNow OOB integration's webhook event listener currently has no mechanism to verify that an incoming payload actually originated from our ServiceNow instance — there's no signing secret / signature header support. This is required for the ServiceNow integration for verifying the source.

Add native support in the GitHub Ocean integration to enrich githubUser entities with email addresses sourced from organizationVerifiedDomainEmails

The GitHub Ocean integration should ingest membership data for GitHub Enterprise Teams ( ent:* slugs) in the same way it does for standard organization teams. Today, enterprise teams are discovered and synced as team entities in Port, but their member relationships are not populated. The enrichment flow relies on GraphQL organization.team(slug) , which returns null for enterprise-managed teams ( ent:* ), causing member enrichment to be skipped while the team entity itself is still created. As a result, enterprise teams appear in Port without their members, creating an inconsistency between enterprise-managed teams and standard organization teams. This feature request is to add support for ingesting and maintaining membership relationships for GitHub Enterprise Teams.

Currently, the GitHub Ocean integration requires users to use a GitHub personal access token (PAT) in order to ingest multiple GitHub Organizations into Port using a single GitHub Ocean integration. In the future, the GitHub Ocean integration should offer alternative authentication methods to allow users to ingest multiple GitHub Organizations using a single GitHub Ocean integration.

We would like to connect monitors to users through roles, roles have an API to help with this that will return all users related to a role.

Add official support for AWS GovCloud environments in AWS integrations. At present, customers operating in GovCloud experience failures because the integrations assume standard commercial AWS ARN formats and depend on AWS APIs that are not available in GovCloud regions.

We'd like to have the following fields populated by the github-ocean-pr integration for Pull Requests: lines_added, lines_deleted, files_changed, commit_count, reviewers (approved, changes requested by, commented by with timestamps), ci_status (checks API).

The Port Execution Agent currently offers limited insight into its runtime version and the API requests it makes to Port (polling, status reporting, log pushing), which hinders troubleshooting, auditing, and version management in production environments.