Get Epic to appear in Board and Backlog

[Gordon Robertson]

I have a team-managed project using Kanban. The option to create an Epic on the Board or Backlog is missing, and if I create one using the Create button at the top, then upon saving I get a message that it has been create, but "to be visible, it must match your project and filters, and have a status that’s assigned to the board.

My board has no filter created. If I check the filters, it states I can create a custom one. When I check within Configure Board, I am taken to the Columns and statuses page which shows all issue types including Epic have been added already.

I have read over many other questions with the same issue, but it seems people just ask if the above is configured and then stop responding. None of the threads I found have a solution to the problem.

Hoping someone can help as I am completely lost with whatever it is doing, and to me it just looks like Jira got a lot worse since it moved to the cloud (my old local install just worked)

[Trudy Claspill]

Hello @Gordon Robertson 

Welcome to the Atlassian community.

I want to first make sure that I have noted your scenario correctly:

1. You are working with a team-managed software project.
2. You do have the Board feature enabled.
3. You do not have the Sprint feature enabled.
4. You do have the Backlog feature enabled.

In Team Managed Software projects, Epics do not display as cards in the Backlog nor on the Board.

In the Backlog Epics may be shown only in the Epics panel.

In the Board Epics will not be shown as cards at all. If you use the Group By: Epics option the any Epics that have child issues will display as swimlanes.

Using the +Create option in either location will not allow you to create an Epic type issue. Those can be created only using the Create button in the menu bar.

So far I have not been able to replicate the scenario of 

1. Having the native Board of the Team Managed project displayed and then
2. Using the Create button to create an Epic type issue in that same project and then
3. Getting the error message about the Epic not being visible.

Could you possibly recreate this scenario and provide a video capture that you can share with us?

(Side note: I'm stating the following because you are new to the community and may not know. We are a community of users of the Atlassian products, not Atlassian employees or support engineers. We have no access to your environment. We can ask you for more information and suggest debugging options, and potential figure out what has happened based on the information you share. If you want to contact Atlassian support directly, you should open a support case at https://support.atlassian.com/contact/#/ )

[Gordon Robertson]

That all sounds accurate. Replicated the issue with the following steps:

Project > Create Project > Software development > Kanban > Use template > Select a team managed project > Give it a name

Within Project settings > Features > Enable:

- Backlog

- Releases

At this stage, I have verified that Epics are within the workflow, but when I Create one using the option at the top, it only appears within the List section

Thanks

[YY Brother]

Hi @Gordon Robertson 

Welcome to our Community.

I just created an Epic from the top menu of Create and can see it in the Backlog through this way:

According to what you described above, it seems the initial status of Epics is not configured int he Board -> Columns and statuses (in the left Unassigned statuses?). Please check:

Hope it helps,

Thanks,

YY Bro

[Gordon Robertson]

It shows there are 35 issues. 34 are Epics and do not appear on the Board or Backlog

[YY Brother]

see my first sreenshot

[Gordon Robertson]

I saw your first screenshot. All it shows is when you do something it works. When I do it, it doesn't.

If I open the epic panel and create an epic there, it disappears immediately. I can then find it in the List section, but nowhere else. That was why I raised this issue in the first place. Doing what I expect to work, doesn't. So showing me how it should work won't help me, since there seems to be something broken in the backend