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 Jira

27% entity overlap

Import

Jira tracks your epics and stories. UPG asks why they exist.

The structural finding

Jira is the most widely used tool in the space, with the lowest strategic overlap with UPG. Epic → epic and Story → user_story map cleanly. The epic hierarchy inversion is the critical adapter note: a Jira Epic is semantically closer to a UPG feature than to a UPG epic. The 73% gap is the entire strategic, research, design, and business model layers that Jira was never designed to hold.

What UPG adds

1

Strategic context: every Jira epic in isolation. UPG connects it to the outcome it serves, the opportunity it addresses, and the persona it helps.

2

The enrichment flywheel: import your 47 epics, then the AI copilot guides you through building the strategic layer, asking "which business goal does each epic serve?"

3

Cross-domain traversal: from a user story in Jira → through the epic → to the outcome → to the OKR it serves. One graph, one query.

Schema mapping

Direct matches
Issue (Story)→user_story
Issue (Bug)→bug
Issue (Task)→task
Issue (Epic)→epicLiteral mapping, semantically closer to UPG feature; see --semantic-mode flag
Version→release
Component→feature_area
Maps with caveats
Sprint→(no UPG equivalent; sprint is team process)
Custom field "Opportunity"→opportunityDetected via field name pattern matching
IssueLink (Blocks)→dependency
What UPG adds
outcomeopportunitypersonahypothesisinsightobjectivekey_result
Skipped:Boards · Workflows · Permission schemes · Worklogs · Comments

The key edge

The single most important semantic relationship this integration enables.

epic_specified_by_user_story

Defined in the UPG specification

Sample import

A typical delivery tree: Version → Epic → Story → Bug

Input (from Jira)
Output (UPG nodes)
Version
v2.4 Release
→
release
v2.4 Release
Epic
User Authentication
Literal mapping, semantically a UPG feature
→
epic
User Authentication
↳ release_contains_feature
Story
As a user, I can log in with SSO
→
user_story
As a user, I can log in with SSO
↳ epic_specified_by_user_story
Bug
Login fails with special characters
→
bug
Login fails with special characters
↳ release_contains_bug

Roundtrip

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

Import epics and stories → add opportunity and outcome links in UPG → write strategic context back to Jira via Atlassian MCP.

Writes back
  • ·Opportunity descriptions written back to epic fields
  • ·Outcome links surfaced in epic descriptions
  • ·UPG node IDs stored in custom fields for deep traceability

How to import your Jira data

Via the CLI (coming soon)

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

npx unified-product-graph import --from jira

This will fetch your Jira 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 { JiraAdapter } from '@unified-product-graph/adapters'
// Pass pre-fetched Jira data as SourceItem[]
const adapter = new JiraAdapter()
const result = await adapter.convert(items)
// result.nodes → typed UPG entities
// result.edges → canonical relationships
// result.warnings → items needing review

Get started

The Jira 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