Linear Integration — Missing Resource Kind Support
V
Vinnakota Mohith
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.
x
xxx Nimal Sunny
Guys, These are basic resource kinds that should be available out of the box. We shouldn't be needed to raise new 'feature' requests !