What is an epic?
This page is for company-managed projects
To check whether your project is team-managed or company-managed, select more actions (•••) next to the project name in either the header or the sidebar. At the bottom of the menu that opens, you’ll be able to view whether your project is team-managed or company-managed.
More about the difference between company-managed and team-managed projects.
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.
View an epic's work items
You can use the JQL Epic Link field to search for an epic's work items.
Learn more: Advanced searching
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.
Was this helpful?