Working with epics
Are you on the right help page?
Using the classic Scrum and Kanban projects? You're in the right place!
Using a next-gen Software project as part of the new Jira Software? Check out these pages instead.
If you're unsure, check your project menu. If it has the Give feedback and Learn more menu items, you're on a next-gen Software project and this page isn't for you.
On this page:
An epic captures a large body of work—performance-related work, for example—in a release. It's essentially a large user story that can be broken down into a number of smaller stories. An epic can span more than one project, if multiple projects are included in the board where the epic is created.
Unlike sprints, scope-change in epics is a natural aspect of agile development. Epics are almost always delivered over a set of sprints. As a team learns more about an epic through development and customer feedback, some user stories will be added and removed to optimize the team's release time.
There may be differences in how epics are displayed and configured between Scrum and Kanban boards—especially if you're using the kanban backlog in a kanban project. See Managing epics in a Scrum project and Managing epics in a Kanban project for more info.
Linking a Confluence page to an epic
If you have linked your Jira Software site to Confluence, you can create and link Confluence pages to your epics. For example, you may want to link your epic to a specification or design document in Confluence.
Learn more: Linking a Confluence page to an epic
Viewing an epic's issues
You can use the JQL
Epic Link field to search for an epic's issues.
Learn more: Advanced searching
Getting help. Need help? If you can't find the answer you need in our documentation, we have other resources available to help you. See