Epics suddenly not showing in Backlog

[Pip Bennington]

We are using Jira Cloud, Standard subscription.

I have a Company-Managed Software Project with a Board that displays a selection of Epics from across our system using a filter.

Up until this morning it worked perfectly, but something has changed and it is no longer showing Epics in the Backlog.

The Active Sprint displays the Epics that have been pulled it, but the Backlog will not show any Epics.

When I look at the filter I see all Epics, but the Backlog is now empty.

I have checked the columns, and all Epics have the Sprint field

It is using a filter that says "if issuetype = Epic and FieldX is not EMPTY"

I have tried recreating a new project and board it does the same thing.

If I turn on the Epic panel in view settings, I see all the Epics, but not as backlog items

Any suggestions to resolve?

[Solomon O]

@Pip Bennington This behaviour you were used to was actually a bug and it got fixed. However, we understand some users are conflicted on how to implement SAFe.

Kindly reach out Atlassian Support to have us delay this fix for your instance.

[PVS_JoD]

We also have the same issue but on "custom epics", these are custom issue types on the same hierarchy level as Epics. On Monday all "custom epics" were still visible in the backlog view, Tuesday they were gone. They are still visible in the Active sprint view. Enabling or disabling the Epic panel in the backlog view doesn't make any difference. 

[Audrey Lenain]

We are facing a similar issue, we had set our own issue types and the ones on the level 1 hierarchy (same hierarchy place as epics in standard configuration) aren't displaying at all in our backlog, but they are still displayed on the active sprint board. Same issue is happening across different projects using the same configuration.

[Pip Bennington]

Hhmmm sounds like an Atlassian thing if you haven't changed anything either.

[Solomon O]

This behaviour you were used to was actually a bug and it got fixed. However, we understand some users are conflicted on how to implement SAFe.

Kindly reach out Atlassian Support to have us delay this fix for your instance.