Customers using the Aikido Ocean integration needs team ownership surfaced at the issue group level, not just on individual issues. Their teams use included_paths to define responsibility, and while individual Aikido issues map correctly to teams via affected_file, issue groups only expose repository-level data — so the same matching can't be applied.

The natural workaround (relating issue groups → child issues → teams via mirror properties) is blocked by the 500-entity search relation cap, since groups can have hundreds of child issues.

A simple SET aggregation also doesn't meet their needs — because individual issues can belong to multiple teams, they need a distinct list of teams per issue group, making this a true many-to-many relationship.

Requested: Add a native team dimension to the Aikido integration by leveraging Aikido's own team→issue group mapping:

GET /api/public/v1/teams

GET /api/public/v1/open-issue-groups?filter_team_id={team.id}

This would expose a team_issue_groups resource (or equivalent relation on issue groups) with the distinct set of owning teams per group — modelled as many-to-many. Without this, the customer is forced to build and maintain an external scheduled aggregation job.