Working with epics

Still need help?

The Atlassian Community is here for you.

Ask the community

NOTE: Using Jira's new agility board? It's currently in beta development phase, which means you may not (yet) have access to the features described below. 

An epic captures a large body of work, e.g. performance-related work in a release. It is 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 on 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 information.

On this page:

Linking a Confluence page to an epic

If you have linked your Jira Software instance to a Confluence instance, 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

Next steps

 Need help? If you can't find the answer you need in our documentation, we have other resources available to help you. See Getting help.

Last modified on Jan 30, 2018

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.