Working with epics
Planning a version
On this page
In this section
Related content
- No related content found
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.
Depending on whether you use Scrum or Kanban, see Managing epics in a Scrum project, or Managing epics in a Kanban project. In general
The way epics are displayed and configured between Scrum and Kanban boards is mostly the same. See Managing epics in a Scrum project, or 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
Next steps
Need help? If you can't find the answer you're looking for in our documentation, we have other resources available to help you. Check out Getting help.
Read the following related topics:
In this section
Related content
- No related content found