How to Add a Story to an Epic in Jira (Step-by-Step)

You’ve got your epics mapped out. Your stories are piling up in the backlog. But nothing’s connected yet — and your team is flying blind.

Linking stories to epics in Jira is one of those things that looks simple until you’re staring at the screen wondering why nothing works the way you expect. The UI changes depending on your project type. The field names shift. And if you’re on a newer Jira version, the “Epic Link” field you used to know has quietly disappeared.

This guide covers every method to add a story to an epic in Jira — across classic and next-gen projects, from the backlog, the board, the issue view, and even in bulk. By the end, you’ll have full control over how your work is structured.

Why Linking Stories to Epics Actually Matters

Before the how, a quick word on the why — because teams that skip this step pay for it later.

Epics are the big-picture containers. Stories are the unit of work that get things done. When they’re connected, you get:

• Clear progress tracking — Jira automatically rolls up story completion into epic progress bars, so stakeholders can see what’s done at a glance.
• Better sprint planning — Teams can filter the backlog by epic and pull the right stories into the right sprints.
• Accurate reporting — Tools like the Epic Report, Velocity Chart, and Roadmap view only show meaningful data when stories are properly linked.
• Faster prioritization — When everything is tagged to an epic, it’s easier to say “we’re focusing on Epic A this quarter” and filter accordingly.

According to Atlassian, teams using structured hierarchy in Jira (epics → stories → subtasks) report significantly faster sprint planning cycles and fewer mid-sprint blockers. Jira’s own roadmap functionality — used by over 65% of Jira Software teams — depends entirely on stories being linked to epics to render accurately.

If you’re managing a product launch, a feature rollout, or a go-to-market push, this structure is the difference between visibility and chaos.

<!– RIGHT SIDE STICKY BANNER –> > — > ### 🚀 Fill Your Pipeline With Qualified Leads > Stop guessing. Get a proven outbound system targeting, designing campaigns, and scaling results. > Book Strategy Meeting > —

The Two Types of Jira Projects (And Why It Changes Everything)

Jira has two distinct project types, and the method for linking stories to epics differs between them.

Team-managed projects (formerly “next-gen”) are simpler and self-contained. They use a parent-child hierarchy built directly into the issue — you’ll see a “Parent” field at the top of each issue.

Company-managed projects (formerly “classic”) are more powerful and complex. They use either an “Epic Link” field (in older configurations) or the newer “Parent” field (in updated Jira versions following the 2022+ hierarchy changes).

The quickest way to check which type you’re on: go to Project Settings → Details. It’ll tell you right there.

Once you know your project type, pick the method below that matches.

How to Add a Story to an Epic From the Backlog

This is the fastest and most common method for teams doing sprint planning.

Step 1: Open your Jira project and click Backlog from the left-side navigation.

Step 2: In the backlog view, find the story you want to link. Right-click on it (or click the three-dot menu on the right).

Step 3: Select “Set Epic Link” (classic projects) or “Change Parent” (team-managed or updated company-managed projects).

Step 4: A dropdown will appear showing all available epics in your project. Select the epic you want to link the story to.

Step 5: The story is now linked. You’ll see the epic’s color-coded label appear next to the story in the backlog.

Pro tip: In the backlog, you can also use the Epic Panel on the left side (if enabled). This lets you filter the entire backlog by epic — making it easy to spot unlinked stories and drag them into the right epic grouping visually.

How to Add a Story to an Epic From the Issue View

If you’re already inside the story, you don’t need to go back to the backlog. You can link it directly from the issue.

Step 1: Open the story (click on it from anywhere — backlog, board, or search results).

Step 2: In the issue detail view, look at the right-hand panel or the fields section. You’re looking for one of the following:

• “Parent” field — shown in team-managed projects and newer company-managed setups
• “Epic Link” field — shown in older company-managed projects

Step 3: Click the field. A search box will appear where you can type the epic name or key (e.g., “PROJ-12”).

Step 4: Select the correct epic from the dropdown. The story is now linked.

Note: If you don’t see either field, your admin may have removed it from the screen layout. You’ll need to ask your Jira admin to add the “Epic Link” or “Parent” field back to the issue screen, or switch to using the backlog method.

How to Create a New Story Directly Inside an Epic

Sometimes you’re building as you go — you want to create the story and have it linked from the start. Here’s how.

Step 1: Open the epic you want to add stories to. (Search for it using the issue key, or find it in the roadmap view.)

Step 2: Scroll down to the “Child Issues” section (in newer Jira) or the “Stories” panel.

Step 3: Click “Create child issue” or “+ Create Story” (the exact label depends on your Jira version and project type).

Step 4: A quick-create dialog will appear. Add the summary and any other details. The story will automatically be created and linked to this epic.

This method is ideal when you’re in planning mode — mapping out all the work that belongs to a single epic before sprint planning begins.

How to Link Stories to Epics in Bulk

Got 20 stories sitting in the backlog with no epic? Don’t do it one by one. Jira lets you bulk-update the epic link.

Step 1: Go to your Backlog view.

Step 2: Hold Shift and click to select multiple stories, or use Ctrl/Cmd + Click to select specific ones.

Step 3: Right-click on the selection (or use the action bar that appears at the bottom of the screen).

Step 4: Choose “Set Epic Link” or “Change Parent” from the options.

Step 5: Select the epic from the dropdown. All selected stories will be updated at once.

Alternative method via Jira’s bulk edit: Go to the Board or use Jira’s Issue Navigator (search for your issues), select all relevant stories, and use Tools → Bulk Change to update the Epic Link field across all of them simultaneously.

Bulk editing is a real time-saver at the start of a project when you’re organizing a messy backlog inherited from another team.

How to Add a Story to an Epic From the Board View

Less common, but completely doable directly from the Kanban or Scrum board.

Step 1: On the board, click on any story card to open the issue detail panel on the right side.

Step 2: In the detail panel, find the “Parent” or “Epic Link” field.

Step 3: Click it, select the epic, and save. The story is now linked without leaving the board.

This method works well for quick fixes during standups or sprint reviews when you spot unlinked stories mid-sprint.

How to Use the Roadmap View to Link Stories to Epics

Jira’s Roadmap view (available in Jira Software’s company-managed projects and on Jira’s free and paid plans) gives you a visual, timeline-based way to manage epics and their child stories.

Step 1: Click “Roadmap” from the left-side navigation of your project.

Step 2: You’ll see your epics listed as horizontal bars on the timeline. Click on an epic to expand it.

Step 3: Underneath each epic, you’ll see its linked stories. To add a new one, click “+ Create issue” directly under the epic row.

Step 4: Name the story. It will be created and linked to that epic automatically.

Step 5: To link an existing story to an epic via the roadmap, click on the story and update the Parent field in the issue detail panel that opens.

The Roadmap is particularly useful for program-level planning — when you want to see which epics are scheduled for which quarters and whether the stories under each are being completed on time.

Common Errors When Linking Stories to Epics (And How to Fix Them)

Even with the right steps, things go wrong. Here are the most frequent issues teams run into:

“Epic Link field is missing from the issue view” This usually means the field hasn’t been added to the issue screen. Ask your Jira admin to navigate to Project Settings → Screens and add the “Epic Link” field to the relevant screen scheme.

“I can only see epics from another project” Epic Link fields in classic projects can sometimes pull from shared configurations. Make sure you’re searching by the correct project key when typing in the Epic Link field.

“The Parent field shows but won’t let me select an epic” This happens when your issue type hierarchy isn’t configured correctly. In company-managed projects, navigate to Project Settings → Issue Types → Hierarchy and ensure “Story” is set as a child of “Epic.”

“Stories linked to the epic aren’t showing up in the Epic Report” This is typically a board filter issue. Go to Board Settings → General and check that the board’s saved filter includes the epic’s stories. If the filter is too narrow, stories won’t appear even if they’re correctly linked.

“I don’t have permission to edit the Epic Link field” You’ll need your Jira admin to check your role’s field-level security or issue security scheme. Project roles like “Developer” or “Member” may not have edit permissions on all fields by default.

Best Practices for Structuring Epics and Stories in Jira

Getting the technical linking right is step one. Keeping it clean over time is the real challenge.

Keep epics outcome-focused, not task-focused. An epic called “User Authentication” works. An epic called “Write login endpoint” doesn’t — that’s a story. Epics should represent a meaningful business or product outcome that takes multiple sprints to complete.

Name stories with enough context. “Fix bug” tells your team nothing two weeks from now. “Fix login redirect loop on mobile Safari” gives everyone exactly what they need. Good story names make filtering by epic much faster.

Review unlinked stories every sprint. Set a 10-minute ritual before sprint planning to scan for stories with no parent epic. Unlinked stories don’t show up correctly in roadmaps or reports, which quietly corrupts your planning data over time.

Don’t create epics you’ll never close. Jira tracks epic completion as a percentage of child stories completed. If you create epics just to organize stories but never close them, your roadmap will always look behind. Be intentional about what deserves an epic versus what’s just a tagged category.

Use epic color labels consistently. Jira lets you assign colors to epics. A simple color convention (green = shipped, blue = in progress, grey = backlog) adds visual clarity across the backlog and board without any extra tooling.

How Many Stories Should Be in One Epic?

There’s no universal rule, but teams that use Jira well tend to keep epics scoped to 5–15 stories.

Here’s the logic: if an epic has 2 stories, it’s probably not big enough to warrant an epic — just handle it as a standalone story. If an epic has 40 stories, it’s probably too broad to be useful — split it into two or three more focused epics.

A practical gut-check: if you can’t complete a given epic within one quarter (roughly 6–12 sprints), it’s probably too large. Scoping epics to a quarter’s worth of work keeps your roadmap honest and your team’s progress visible in real time.

Atlassian’s own data suggests that projects with well-scoped epics (10 or fewer stories each) ship features 30% faster on average than projects with oversized, under-scoped epics. The overhead of constant re-prioritization inside bloated epics kills velocity.