How Do You Import Jira Epics into Deck?
Connect Jira in Settings → Integrations, then open Build → Projects and choose the Jira import option. Each epic you pick becomes a Deck Project linked to that epic, optionally under an initiative. Nothing changes in Jira, any member can import, and imports use no credits. Each Project can then carry the customer evidence behind it.
Why Jira Epics Lose the Customer Context
Epics in Jira say what the team will build, not who asked for it. The customer quotes that justified an epic sit in support tools and call notes, far from the ticket. When priorities shift, nobody can show which epics customers need and which ones they never mentioned.
How Deck Ties Jira Epics to Customer Evidence
Deck imports each Jira epic as a Deck Project and keeps it linked to the epic. Jira stays where the team delivers. Deck refreshes the title, status, and owner daily, while the Project's documents and customer evidence stay in Deck, so each epic carries the feedback behind it.
How to Import Jira Epics into Deck
Run it yourself in Deck, or hand it to your AI agent. Same steps, same result.
- 01
Connect Jira
An organization admin opens Settings → Integrations, picks Jira, clicks Connect, and completes the Atlassian authorization. Jira does not count toward the Free plan's one-integration limit.
- 02
Choose Which Epics to Bring In
Set the scope: one Jira project, a text search, or all epics. Deck links each Project to one Jira epic. Jira projects are only the containers the epics live in.
- 03
Check for Projects That Already Cover an Epic
Look through Build → Projects for work that matches an epic. Link those instead of importing, so you do not create duplicates. Skip epics that are already linked in Deck.
- 04
Import Each Epic
Open Build → Projects and choose the Jira import option. Select the epic, optionally pick the initiative it belongs to and a segment, and confirm.
- 05
Link Existing Projects to Their Epics
Open the Deck Project, open the external handoff menu, and choose the Jira link option. Deck fills only empty fields from Jira and does not overwrite your title, owner, Overview, or Evidence.
- 06
Check the Customer Evidence
Open each imported Project's Evidence tab to see what customer evidence it has. A Project with few linked insights needs evidence before it earns its place. As new feedback arrives, Deck can attach high-confidence matches to it on its own.
Import Jira Epics with Your AI Agent
Prefer Claude, ChatGPT, Cursor, or another MCP client? Paste this prompt. Your agent runs the same workflow through Deck MCP and checks with you before it changes anything.
You need
- Deck MCP connected to your agent
- Jira connected to Deck
Your agent starts with explore_integrations.
Agent Prompt
Paste This into Your Agent
Use Deck MCP. Fetch and follow https://docs.getdeck.io/docs/agents/workflows/import-jira-epics.md
Jira Epic Import Plan
Epic key | Title | Status | Owner | Action | Deck initiative | Segment----------|--------------|----------|---------|----------------------|----------------------|------------------[KEY-123] | [Epic title] | [Status] | [Owner] | Import / Link / Skip | [Initiative or none] | [Segment or none]## Scope- Jira project key: [KEY or all]- Search: [text or none]## Actions- Import: Not in Deck yet. It becomes a new Deck Project.- Link: A Deck Project already covers it. Link it instead of importing.- Skip: Already linked in Deck. Open it from its Deck link.## After the importEpic | Result | Deck link | Linked insights----------|----------------------------------------|-------------|----------------[KEY-123] | Imported / Linked / Skipped ([reason]) | [Deck link] | [Deck count]