Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Can't find children of an epic, feel like I've checked everything

Calvin
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 20, 2025

Hi all, we have this plan set up in jira Software Cloud, it is epic > Story and the source is a whole project (plus the projects boards).

But for a particular epic it won't show the children of it. If I add a new story it will show that child of the epic, created the some way via parent. But current ones don't?

I have also double checked the tickets are not "excluded" in exclusion list, and I can't imagine it is some view as it shows new stories as children in the plans and it shows stories under other epics.

I don't know if I'm missing something, could it be related to our recent migration from data centre to cloud where we used to use "Epic link".

Cheers

---------------

Edit I'm really having a lot of trouble understanding Plans. I created a filter of just the project and can confirm a bunch of Epics including this one. I then created a new plan and added this filter as the source. And now this epic doesn't even appear? Why? Its in the filter, the other epics work? Its not because its completed/done/resolved.

1 answer

1 accepted

0 votes
Answer accepted
Calvin
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 20, 2025

Ahhhh found the issue. Turns out in the exclusion area of plans, even though it says "0 work items removed (based on type, status or completion date)."

It doesn't actually count the ones removed by DATE. As such it hid all the epics made past the default date in there even though it says it didn't. Changing this to a big number brought all these work items back.

Ack. Turns out it is the exclusion section that did it.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events