JIRA Epics and Roadmaps
Stories and tasks describe small pieces of work. Leaders and customers care about bigger goals, such as launching an online store or redesigning a mobile app. Epics group small items under one big goal, and roadmaps display those goals on a calendar.
Layman's View: Planning a Holiday
Planning a trip to Goa is the big goal. Booking flights, reserving a hotel, and listing beach activities are the smaller jobs. The trip is the epic. Each job is a story or task that belongs to it.
EPIC: Online Store Launch | +-- Story: Product listing page | +-- Story: Shopping cart | +-- Story: Payment gateway | +-- Bug: Cart total shows wrong amount
Epic, Story, and Task Compared
Work Item Levels in JIRA
| Level | Size | Typical Duration | Example |
|---|---|---|---|
| Epic | Large goal | Several weeks to months | Launch customer portal |
| Story | One user-facing feature | Days to one sprint | Customer resets a password |
| Task | One piece of work | Hours to days | Set up email server |
| Subtask | One step of a task or story | Hours | Write test cases |
Creating an Epic
- Click Create and choose Epic as the issue type.
- Write a name that states the goal in plain words.
- Add a short description with the purpose and expected result.
- Set an owner and optional start and due dates.
- Save the epic.
Adding Work to an Epic
Stories, tasks, and bugs join an epic through the parent or epic field on each issue. Many teams drag issues onto an epic in the backlog view. Some JIRA versions label this connection Epic Link, and newer versions label it Parent. Both labels describe the same idea.
Tracking Epic Progress
An epic shows a progress bar that counts child issues in each status. Green marks finished work, blue marks active work, and grey marks work not started. Managers read the bar in seconds without opening every card.
Epic: Online Store Launch Progress [#########-----------] 45% Done: 9 issues In Progress: 4 issues To Do: 7 issues
Roadmaps: The Big Picture on a Calendar
A roadmap places epics on a timeline. Each epic appears as a horizontal bar that stretches from its start date to its due date. Product owners, executives, and customers read a roadmap to learn what ships and when.
Jan Feb Mar Apr May
Epic A [==========]
Epic B [===============]
Epic C [=================]
Epic D [=========]
How to Read a Roadmap
- Bars that overlap show work running at the same time.
- Long bars show large goals that need more effort.
- Gaps show free capacity or planned waiting periods.
- Dependency lines show epics that must finish before others start.
Who Uses Roadmaps
Roadmap Audiences and Their Questions
| Audience | Question They Ask |
|---|---|
| Executives | Which goals ship this quarter? |
| Product Owners | Does the order of epics match business priority? |
| Developers | What work arrives after the current sprint? |
| Customer Support | When does a requested feature arrive? |
Roadmap features differ by JIRA plan and project type. Check the available options in your own site before planning a rollout.
Good Habits for Epics
- Name each epic after an outcome, such as "Customers pay by card", and avoid vague names like "Phase 2".
- Size epics so they finish within a few sprints. Giant epics hide progress.
- Close finished epics promptly so the roadmap stays readable.
- Review dates monthly. Plans shift, and the roadmap must reflect reality.
Real-World Example
A bank team plans a mobile app refresh. The product owner creates three epics: New Login, Faster Payments, and Account Insights. Each epic holds around twelve stories. The roadmap shows New Login in January and February, Faster Payments across February to April, and Account Insights in May. Executives scan the picture in one meeting and approve the order without reading a single story.
Summary
Epics group related stories, tasks, and bugs under one large goal. Progress bars show how much of that goal stands complete. Roadmaps lay epics along a timeline so every stakeholder sees the plan at a glance. Clear names, sensible sizes, and regular reviews keep both tools useful.