Some Epics from Jira Project not visible in Plans

[Martin Rait]

I've set up an a plan using a filter, and one of 3 Epics are not appearing.

I've tried the filter with this:

parentEpic in (BIZ-39, BIZ-1 BIZ-26) order by created DESC

and this:

parentEpic in (BIZ-39, BIZ-26) or parentEpic = "BIZ-1" order by created DESC

But BIZ-1 Epic and child tickets do not appear in Plan, while the other 2 appear fine.

The Filter itself returns the correct result set.

Anyone know what is going on?

[Daniel Capizzi · Accepted solution]

Hi @Martin Rait

Your first JQL is missing a comma after BIZ-1, but as you mentioned when you look at the filter itself it returns the correct set of issues, so I'm assuming that might just be a transcription error here? If so, it's likely that your BIZ-1 Epic is being captured by some sort of exclusion rule.

By default, a newly created plan will exclude issues that have been in the "Done" status for more than 30 days, so if your BIZ-1 Epic was moved to Done more than a month ago that could be why it's not showing up.

Otherwise, you can check any other exclusion rules by clicking the three dot menu next to your plan name, selecting "Configure"  and then "Exclusion Rules". Comparing the rules configured here to your BIZ-1 Epic may reveal why it's being excluded.

Hopefully this helps resolve the issues you're having, but let me know if you're still having trouble and we can certainly dig into this a little deeper!

Cheers,

Daniel

[Martin Rait]

missing comma is a typo for mine typing here.

The 30 day thing is annoying and appears to be what is going on - do many different areas to configure things. Resolved that and found it hiding releases as well.

We needed this to be a full client facing plan - so all work done needed to be present.

Thanks

[Daniel Capizzi]

No problem Martin - I'm glad that resolved the issue for you.

I can definitely understand that Advanced Roadmaps can be a bit of a beast to get familiar with! We're always trying to improve so I'll pass your feedback on to the team, and do always feel free to reach out here for any further questions you have or at Atlassian Support for more in-depth support.

[Joseph Chung Yin]

@Martin Rait -

Hi Martin:

I am glad that you found the issue.  So you just need to ensure you configure the "Exclusion Rule" to fit your needs. 

As also mentioned in my previous answer, the "Exclusion Rule" often is the problem because it is always defaults to 30 days setting when a plan is created.

Lastly, you should also adjusted it so your plan only display most relevant issues instead of everything.  It is because there can be performance impacts + too many issues are being displayed to allow your users to focus on.

If my advise also helped you.  Please click on Accept Answer when you have a chance.

Best, Joseph

[Joseph Chung Yin]

@Martin Rait -

Welcome to the community.  When you referring "Filter" are you referring to the issue source from the plan's configuration UI?

If not, then you need to check your issue source setup and ensure the source contains those missing EPICs.  

If yes, then you need to check the "Exclusion Rules" area in the plan's configuration UI to determine if there are any rule setup which excluded your missing Epics.  Lastly, you should also check the "Removed Issues" area in the plan's configuration to see if those issues are displayed, if you sees them there, you can click on "Re-include" button to bring those issues back into your plan.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

[Indranil Ghosh]

@Joseph Chung Yin Could you please help me find the "Exclusion Rules" section and the "Removed Issues" section? I am not able to find these in the configuration section.

[Joseph Chung Yin]

@Indranil Ghosh -

Welcome to the community.  You will need to access your plan "Plan settings" and then select the "Configure" option.  In the configuration UI, you will find what you are asking for.

Best, Joseph

[Wagner Nunes]

Hi all, I'll be honest, it amazes me how a feature like Plans/Advanced Roadmaps still doesn't work properly after this long.

After googling about this issue extensively, I see there is a significant amount of people out there facing the same issue with Epics not showing up in the view despite being correctly linked to their Initiatives via Parent Link field and meeting the other criteria.

We've checked all the settings/config and we still can't figure out why Epics aren't showing.

Hi @Joseph Chung Yin @Daniel Capizzi - could you please provide some more details troubleshooting guidance here?

I've gone through the all usual vanilla answers around "have you checked the exclusions, have you checked issue sources" and the likes so I'd appreciate any further/more detailed guidance anyone can provide. Thanks.

[Daniel Capizzi]

Hi @Wagner Nunes - totally get how frustrating it is not having visibility over why issues aren't showing up, sorry it's been a poor experience.

Unfortunately, I can't say too much beyond the standard suggestions without knowing a bit more about your setup. We have a page written up with a few more common reasons that issues might not be appearing which may be useful to you though - one of the most common reasons is the issue being Resolved for more than 30 days.

https://support.atlassian.com/jira-software-cloud/docs/troubleshoot-missing-issues-in-your-plan/

Otherwise, I would recommend getting in touch with us through support. This will allow our support engineers to take a proper look at your plan and help troubleshoot why your issues are missing. https://support.atlassian.com/contact/#/

Cheers,

Daniel

[Rinaldi James Michael]

There's a bunch of settings in Advanced Roadmaps that can make debugging missing issues a nightmare. Easiest ways to check are Exclusion rules and Issue source.

[NCEpTicIDy]

I came across this forum post as I had the same issue. As obvious at it sounds in hindsight, I'd simply not realised that the plan is collapsed by default. I spent half an hour scouring the internet and trying everything before I released my problem was just this: