Skip to end of metadata
Go to start of metadata

An epic captures a large body of work. It is essentially a large user story that can be broken down into a number of smaller stories. It may take several sprints to complete an epic. 

An epic can span more than one project, if multiple projects are included in the board to which the epic belongs.

This page describes how to view epics. Read the following topics to learn more about working with epics.

Viewing an epic

Go to the Backlog to see a list of epics at the left of the screen. Drag-and-drop epics to re-order them (note, this also changes how they are ordered in the Active Sprints). Click an epic's name to view all the issues belonging to that epic, across all sprints (see screenshot below).

Note:

  • Filtering by version takes precedence over filtering by epic. This means that if you have a version selected on your board (see Planning a Version), then epics that do not have any issues in the version will be greyed out.

Screenshot: viewing an epic in the Backlog

You can also view an epic issue in JIRA to see a list of the stories (issues) it contains:

Screenshot: viewing an epic in JIRA

(tick) You can also use the JQL Epic Link  field to search for an epic's issues — see the JIRA JQL documentation for details.

29 Comments

  1. Please create a filter/quickfilter in the reporting section where we can filter for Done/Not Done Epics. Currently all the done Epics are in the list, and no idea how to get rid of them, We are mostly interested in viewing the current Epics on the reporting page, but it is full of old, already Done epics. There are occasions where we want to review the finished epics, the we could use this filter to show the Epics which are already closed.

    1. For anyone coming across this with the same question - setting an epic's Status to Closed won't hide it from the dropdown.But you can hide it using the dropdown on the epic panel of the Backlog to mark it as Done, which hides it from the panel. It uses a separate field, "Epic Status," for some reason.

  2. Agreed!  This would be ideal so that the view is not so overwhelming.  

  3. If viewing a task with sub-tasks in JIRA, the "Sub-tasks" list includes Original/Remaining Estimate bar-charts, and percent worked, for each sub-task. And the "Time Tracking" panel allows all sub-task time to be rolled up into an overall total. This means you get a simple overall picture of the parent task's workload, and the sub-tasks' progress, which is very useful.

    Is there any way to get the same behaviour but for Epics and "Issues in Epic", when viewing an Epic?

  4. Similarly, is there any way to base swimlanes on Epics, on a Kanban board?

  5. BUMP. Someone just asked me how to show the time rolled up to the Epic. We have 10 stories inside an epic. Each story has tasks. Everything has an estimate (from the story on down) Yet the Epic doesn't show the estimated time. What am I missing?

    thanks

  6. We have Epics and stories on multiple Projects. It would be really useful to be able to display in a Scrum Board, Plan mode, list of Epics to:

    • prioritzed them quickly (Some Epics are small on our side)
    • do a quick status with Upper-managment: here is the list of epics we have cross projects.

    Curently we use a Kanban board that Display Epics. Works not easy to Plan (sad)

     

  7. Is there a way to group a bunch of Epics together into a larger trackable Epic?  I have a Big Initiative (Implement xyz website) at the Portfolio level and would like to create Features (which is also an Epic e.g. Landing Page, PGP, PDP, etc.) at the Program level. I know VersionOne has this capability but do not want to switch.  thanks, Kathi


    1. This would be really useful, any way around this today ? sometimes an epic itself is part of a bigger initiative. with no other concept like theme or goal - allowing nested epics would be really useful. 

      1. You could use Confluence for this. We use Confluence to create a Requirement page. This page describes the "big picture"  and it also has links to one or more Epics in Jira. This way, we keep track of the higher level requirements.

         

        Also, when an epic link is added to the Confluence page, you can jump to this page from the Epic in Jira.

      2. Dinesh Rajwani, with our Structure plugin you can group Epics under any other issues (section titled Breaking the Agile mold) and get numerical values (estimates, story points, etc.) and progress rolled up into them.

        1. Looks promising, we would certainly give it a try.

  8. Does anyone know how to drag an Epic to a version in the plan board?

    1. Epics are issues that live in projects.  Projects have their own versions.  Long story short, don't think you can drag an epic to a version.  

      You can, however, have epics showing up for various projects through the Agile board configuration.  Just make sure your board query will include content from more than one project (e.g., project in ("Project 1", "Project 2").  All of your epics from each project will show up on the same board.  You can also have versions from the different projects showing up on the same board via the same method (by modifying your board query).  You may need to add identically named versions to your projects (so that Project 1 has a version called Version 3 and Project 2 also has a version called Version 3), if your projects all feed into a master version.

      If you really want to get fancy, you can have project-specific boards where you manage inside the project, and then have one central board that you use for planning (that essentially brings in all of your epics, projects, and the project versions into the same board).

  9. Hello! Please add showing time estimates for epics (as for usual tasks with subtasks) in "Issues in Epic" section (smile)

  10. I have 2 questions about epics:

    1. What's the difference between creating an issue inside an epic and creating a sub-task?
    2. If I use Agile in Work mode, the epic shows up in addition to the epic issues. Why is that? Shouldn't the epic move along through the states based on how its issues move?

     

  11. Hi,

    It seems like the epic visibility across rapid boards is somewhat surprising. I have not completely troubleshoot yet but it seems like the following scenario works:

    1. create a board A (for a whole project)
    2. create epics
    3. create another board B (for a sub team for instance)
    4. epics created at step 2. are visible on the board B

    However, once the board B is created, it seems like if you create epics from board A, then they are not visible on board B.

    Anyone aware of a workaround to force sync the 2 boards ?

    1. Changing the filter for the board will let you get the epics to appear on more than one board.  Remember that epics are issue types like bugs and new features – if your filter criteria don't include epics, add the epics.  

  12. hi,

    As shown above in top most screen shot ( named as Screenshot: viewing an epic in Plan mode), you have shown fields like issue, completed, un-estimated and estimate under citrus EPIC.

    For my various EPICs, I see the similar view. However, I would like to customise it by adding few additional details. I tried to find out the way, however couldn't get much help on that front.

    My query is:

    1) Is there a way I can customise this view. I would like to add few fields like delta of remaining estimate for that EPIC

    Please advise.

     

     

  13. I currently have a backlog of ~100 issues that are large stories. However, I didn't enter them into JIRA as epics (side note: I do have about 8 epics created and these stories are associated to them). But we're about to begin actual development and we'll be breaking these large stories down into very small ones when we take them into a sprint.

    Since I didn't create them as epics to begin with, am I going to have to create an epic for each one of these and then delete the large story?

    I'd really like to be able to breakdown a story of any size into smaller stories easily when it's time to develop them and this seems like an inordinate amount of work to do that. If I want to break an 8 into a two 3 point stories and 3 one point stories, is there an easy way to do this?

  14. I have a user that wants to have an issue Story accessible by several Agile boards.  Is that even possible?  Sounds insane to me.  Comments/Suggestions?  Thanks

    1. Michael Dugan, this is perfectly feasible, since a board corresponds to a query. As long as the issue is present in the query corresponding to the board, it will be present across multiple boards.

      I personally use this in order to have different views (per theme, per team, per sub-project, you name it) of the same actual product, and especially useful for EPICs that can be part of more than one "view"

  15. We've had an issue where an issue was on two boards with the sprint names the same.  When the issue was closed on one board all the issues on the other board went to the backlog.  I've been told this can be solved by naming sprints unique to each board.  Have you experienced this?

    1. You mean when you closed the Sprint, not when you closed the issue ?

  16. NO, when the issue was worked on one board, it was assigned to someone on another team, and closed, the sprint on the other board went to the backlog!  I've raised the issue with Atlassian and they mentioned that sprint names should be unique.  Really weird.  And this is a bit worrisome.

    1. I never encountered this issue, but my sprints are actually the same accross the boards. Or said otherwise, an issue is only assigned to one Sprint no matter the board.

  17. Ok, thanks Jérôme.

  18. Now, with release of 6.6.51 this page needs to be update to reflect the fact, that Kanban can use epics in swimlanes, too!

  19. Tip: With the plugin "Epic Sum Up" you have some nice time feature (estimated, worked, over estimated, won time, ...) for an epic within all the sub issues/sub tasks:
    https://marketplace.atlassian.com/plugins/aptis.plugins.epicSumUp
    Hope it helps you!