# Import Jira Epics and Back Each One with Customer Evidence

Import Jira epics into Deck as Projects, keep each one linked to its epic, and attach the customer evidence behind the work. Nothing changes in Jira.

- URL: https://getdeck.io/playbooks/import-jira-epics
- Author: Matt Teixeira
- Published: 2026-11-01
- Updated: 2026-11-01
- Stage: Set up

## 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.

Deck features used:

- [Projects](https://getdeck.io/product/projects)
- [Integrations](https://getdeck.io/product/integrations)

## How to Import Jira Epics into Deck

### 1. 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.

### 2. 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.

### 3. 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.

### 4. 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.

### 5. 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.

### 6. 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

You need:

- Deck MCP connected to your agent
- Jira connected to Deck

Your agent starts with the `explore_integrations` tool.

Paste this prompt into your agent:

```text
Use Deck MCP. Fetch and follow https://docs.getdeck.io/docs/agents/workflows/import-jira-epics.md
```

Full agent workflow: https://docs.getdeck.io/docs/agents/workflows/import-jira-epics.md

## Jira Epic Import Plan

### Jira Epic Import Plan

```text
| 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 IMPORT
| Epic | Result | Deck link | Linked insights |
|---|---|---|---|
| [KEY-123] | Imported / Linked / Skipped ([reason]) | [Deck link] | [Deck count] |
```

## Frequently Asked Questions

### Does importing change anything in Jira?

No. Imports read Jira and create Deck Projects only. Unlinking removes only the Deck-side link and does not delete or change the epic.

### Who can import Jira epics?

Any member can import an epic. Only an organization admin can connect Jira, in Settings → Integrations.

### Does it use credits?

No. Imports spend no credits, and Jira does not count toward the Free plan's one-integration limit.

### Why does a Project link to an epic and not a Jira project?

Deck treats Jira projects as containers for epics. Each Deck Project links to one Jira epic, and each epic can link to one Deck Project per organization.

### What stays in sync after the import?

Deck refreshes the title, status, and owner of linked epics daily. It does not fill or sync Jira start and target dates, because those fields differ between Jira setups. Documents and evidence stay in Deck.

### Can my AI agent run this?

Yes. With Deck MCP connected, paste the prompt on this page. The agent lists the epics in scope, flags the ones already in Deck, and shows you an import, link, or skip plan. It asks before it imports, links, or creates an initiative.

## Related Playbooks

- [Import Your Linear Roadmap and Link It to Customer Evidence](https://getdeck.io/playbooks/import-linear-roadmap.md): Import Linear initiatives and projects into Deck, keep each one linked to Linear, and back every roadmap item with customer evidence. Nothing changes in Linear.
- [Validate Your Product Roadmap with Customer Evidence](https://getdeck.io/playbooks/roadmap-evidence-check.md): Find the initiatives and Projects with little customer evidence, link the evidence Deck already has, and see what your team is building on gut feel.
- [Build Features from Customer Evidence, Not Guesswork](https://getdeck.io/playbooks/build-from-evidence.md): Turn a Deck Project into a shipped change where every requirement links to the customer insights behind it. Build it yourself or with your coding agent.