Add Linear Issue Relations to Fivetran
Answered
Connector name: Linear
Table name: ISSUE_RELATION
API documentation link: https://studio.apollographql.com/public/Linear-API/variant/current/schema/reference/objects/IssueRelation
Additional details: The Linear connector syncs `ISSUE` and related tables into Snowflake, but does not sync peer issue relationships (`related`, `blocks`, `duplicate`, `similar`). These are distinct from sub-issue hierarchy (`ISSUE.PARENT_ID`). We need an `ISSUE_RELATION` table with `id`, `issue_id`, `related_issue_id`, `type`, `created_at`, `updated_at`, `archived_at`, and standard Fivetran metadata columns to analyze cross-team linked issues (e.g. Product ↔ Implementation dependencies). Airbyte's Linear source already syncs an `issue_relations` stream.
https://docs.airbyte.com/integrations/sources/linearhttps://linear.app/docs/airbyte
-
Official comment
Hi Tripp, thank you for the request.
Adding support for peer issue relationships is a valuable idea for analyzing cross-team dependencies, and we have added it to our feature improvements backlog. We have confirmed that the relevant relationship data is available in Linear's API. Could you share more about how you plan to use the relationship types, for example, whether blocks and duplicates are equally important to your analysis? We will keep you updated on this thread as we make progress.
Best,
Syead Mujtaba Imam Rizwi -
Yes, we are interested in “related”, “blocks”, “duplicate”, etc., equivalent to the API. Duplicate is the least important, but “blocks” and “related” are equally important. This is how you know that an issue in one project is stopping another from progressing for example. We are also interested in tracking history for this entity, although the API only provides current state.
Please sign in to leave a comment.
Comments
2 comments