Why does my Epic not show up on the scrum board? (Jira Agile)

[Mark Jochemsen]

I have added an Epic from the Backlog screen in JIRA Agile, however it never shows up in the list of epics (which is empty)

Some more information:

• The Epic does show up in the backlog
• The list of issue types in the Administration panel has four types called "Epic", all with the same icon and description.
• The Filter for the scrumboard looks as follows: "project = KROWD ORDER BY Rank ASC"

[Simon Kegel //SEIBERT/MEDIA]

Hey Mark,

this is more kind of a feature than a problem -
in a sprint (your work board) you simply don't work on an epic but on stories and subtasks instead which you break down out of your epics. A epic is just a too big object to resolve it in a sprint or even in multiple. 

Epic is more of an object for clustering your tasks / projects on the backlog and for tracking the progress of the epic and its stories and tasks.

Greets
Simon 

[Samuel Araiza]

[deleted]

[Oleksandr Dykopavlenko]

Hi!

Check if the option 'Epics panel'  is set to 'Yes' (at Board -> Configure -> Columns)

If yuo set the option to 'No', then Epic start appearing in the Kanban board

[Jira-Viv]

It works! Thanks!

[Ryan Jensen]

Hey there, I'm having the same issue where Epics don't appear in Kanban, but I can't find the column setting in Board settings to change. Did this change recently?

[Fabrice So]

We also have the same problem which is a problem when we are working on an epic with multiple teams. Each team has their own project and all have the stories within the same epic. Unfortunately, the epic only shows up if we apply a specific label and query for it. This is very inconvenient and we miss stories unless we apply the label workaround. A few months ago, if a team had an issue under an epic, it would show up on their planning board. Now it needs to be queried explicitly.

[Samuel Araiza]

I would advice for each team to have their own epic if each team already has their own project. That way each team can see how many stories they're responsible for and how many are left. It also helps define when a team is 'done' with an epic. You can then create an epic of epics for project managers to tickle each other over.

[Sourabh Jagavkar]

Hi, I am facing an issue. In my scrum borad I am only able to see user stories that belong to one epic. In the epics panel I see only this one epic. However there are other user stores that belong to different epics (all these epics are in the same project). I want to see all the user stories that belong to different epics so I can plan my sprints and prioritize the backlog accordingly. How to fix this? 

[Mark Jochemsen]

Hi Simon, thanks for your reply! 

This is exactly my issue, as the epic does show up in the list of stories, but not as a group/cluster in the sidebar. 

[Simon Kegel //SEIBERT/MEDIA]

Then put every epic-issuetype in your issuetype scheme for the project KROWD and create an issue with every of the 4. there should be only one which doesn't show in the backlog as an backlog item. this one is the one and only you should use - every other can be deleted or atleast should be renamed.

[Mark Jochemsen]

Thanks for your response! I assigned the "Epic" issue types to my Scheme one-by-one and was able to identify the correct one. Now when I add an Epic, it no longer shows up in the sprint planning backlog. However, on creation I get the following popup: "Your epic XXX has been created but is not currently visible." The Epic still does not how up in the Epic Panel. Any ideas? Thanks

[Simon Kegel //SEIBERT/MEDIA]

Is the Epic from an other project than your board maybe? A board shows only the filtered epics. BoardKROWD = Project KROWD and you will only see KROWD-Epics. BoardKROWD won't so show epics from the project CROWD.

[Mark Jochemsen]

Actually we only use a single project and board. I think the issue might have to do with the fact that we migrated from self hosted to cloud since we can not remove the duplicate Epic issue types. I made a support ticket :) Thanks for your help!

[Naomi_Williams]

I just had this issue and I found that it was because I have the fix version as back log - once I changed that it appeared. :)