Adopt

5 surfaces

Surfaces

Integrations

Strategy & Discovery

2
VistalyProductboard

Research & Insights

1
Dovetail

Knowledge & Docs

1
Notion

Design

1
Figma

Analytics

1
PostHog
DeliveryBeta

Coming from Linear

37% entity overlap

Import

Linear tracks what you're building. UPG explains why you're building it.

The structural finding

Linear is the cleanest delivery tool available. The single most important missing edge: initiative_drives_outcome. Linear Initiatives group projects but have no outcome attached. UPG adds that one typed edge, and suddenly 'did this initiative move the needle?' becomes a graph query, not a meeting.

What UPG adds

1

The strategic layer: outcomes, opportunities, personas, and JTBDs that explain why each Linear project was prioritised.

2

Evidence chains: connect your epics to the research insights and hypotheses that justified them.

3

Import is the beginning: after importing your Linear data, the AI copilot asks "which outcome does each project serve?" and builds the missing layer interactively.

Schema mapping

Direct matches
Issue (feature type)→user_story
Issue (bug type)→bug
Project→epic
Initiative→initiative
Team→team
Milestone→milestone
Maps with caveats
Cycle (sprint)→(no UPG equivalent; sprint is team process)
Label→(property tag on node)
What UPG adds
outcomeopportunitypersonahypothesisinsightresearch_studyobjectivekey_result
Skipped:Comments · Reactions · Notifications

The key edge

The single most important semantic relationship this integration enables.

initiative_drives_outcome

Defined in the UPG specification

Sample import

A Linear workspace: Initiative → Project → Issues

Input (from Linear)
Output (UPG nodes)
Initiative
Q2 Growth
→
initiative
Q2 Growth
Project
Onboarding redesign
→
epic
Onboarding redesign
↳ initiative_drives_outcome
Issue (feature)
Add progress indicator to setup flow
→
user_story
Add progress indicator to setup flow
↳ epic_specified_by_user_story
Issue (bug)
Progress bar disappears on refresh
→
bug
Progress bar disappears on refresh
↳ release_contains_bug

Roundtrip

MCP-POWERED LOOPPlanned
Linear ──import──▶ UPG ──enrich──▶ UPG ──write back via MCP──▶ Linear

Import issues → enrich with outcomes and opportunities in UPG → write strategic context back to Linear via MCP.

Writes back
  • ·Outcome descriptions written back to Linear initiative descriptions
  • ·Opportunity summaries added to epic descriptions
  • ·Strategic context (which OKR this serves) surfaced in issue metadata

Powered by the linear-server MCP server

How to import your Linear data

Via the CLI (coming soon)

The Linear adapter is built and tested. A one-command import via the UPG CLI is in development:

npx unified-product-graph import --from linear

This will fetch your Linear data, map entity types automatically, and write everything to your graph. Today you can use the Markdown import or the adapter directly in code.

▸ For developers: use the adapter directly
import { LinearAdapter } from '@unified-product-graph/adapters'
// Pass pre-fetched Linear data as SourceItem[]
const adapter = new LinearAdapter()
const result = await adapter.convert(items)
// result.nodes → typed UPG entities
// result.edges → canonical relationships
// result.warnings → items needing review

Get started

The Linear adapter ships in @unified-product-graph/adapters. Install it, then run the import command.

# one-time install
$ npm install -g unified-product-graph

# then import
$ upg import --from notion

Other tools in Delivery

← All integrations