Why is JIRA Portfolio showing "Issues without Epics" when the issues are assigned to Epics?

I've been searching through Answers to see if anyone else has this same issue.  I've found: https://answers.atlassian.com/questions/43877274, but that doesn't explain why issues in my "create plan" show up under "issues without epics" when they clearly have an epic and fixVersion assigned?  We are not hiding fixVersion on the project or issues.  Does Portfolio use Epic Link or Epic Theme?  Is there another setting that may be getting in the way?

We're using Portfolio Live Plans v2.1.3.

8 answers

Same issue... 

Same issue.

Ok, so I said I had the same problem, then inspiration hit.

In Portfolio:

> Go to "Configure "(click the elipses to the right of the board name).

> Click "Issue sources"

> Click "Edit sources"

> Run through the steps and ensure when you get to the "Epics" step, you click "Select All." 

> Then finish the configuration steps.

This fixed the issue for me.

Same issue. It is driving me crazy.

0 votes

Same issue. How on earth can something this fundamental be broken and no-one has acknowledged it, no-one has explained how it is going to be fixed, and no-one has given a workaround for it? Why is it not possible to drill into any of these reports and see the underlying data?

I am not sure we'll be able to keep this product, it may be simpler just to build our own reports.

Same issue. Only way I've found to get them to show is to also add the overall Project that the epics are in so e.g. I have a plan based off a team's board and the epics don't show up. If I include the project that the epic is in the epic appears but the downside to it is that anything that is new that gets added to the project also gets added to the plan so you have to keep going into the scope and excluding the issues that aren't relevant to your plan. 

0 votes

Hi Here,


A Portfolio plan only contains and reports on what is part of the plan, this means if the epics are not included (or any other level of hierarchy above story) then the children will be marked as "without a parent"

This goes the other way as well, if you only include a parent it won't have its children.

The solution to it is to ensure the issues are part of the plan issue sources.




Hi Thomas, 

Thanks for your reply. Here's the scenario I have. I have a plan based off a team's Kanban board but the epics don't show up in the configure issue source wizard to even be able to select them. The only way I can see the epics is to add the overall Project as an issue source too. However the overall project is used by many teams across the company so when I add it in as an issue source, anything new that gets added to the project constantly gets added to my portfolio plan even if it is not part of my team's kanban board. I have also tried using a filter for the team and epic but again the epic isn't there to add in only the stories. 

The only way I can find to add the epic is to include the project. There doesn't seem to be any way to use either a filter or a board and include the epic from that. If you've any ideas on how to solve that I would be very grateful!



This is not expected but I haven't been able to reproduce that (for Portfolio for Jira Server), I'd suggest to contact support to help you sort this situation as soon as possible.


Support: https://support.atlassian.com/contact/




0 votes

Thanks Thomas,

All epics and sub-issues from the particular project involved are included (the portfolio plan is built off one project - we are in an ongoing proof of concept). I have reviewed every single issue, one by one, and checked them all. And it tells me there issues missing. I have given up completely on this; without the ability to drill through and investigate the data the use is left frustrated.

This issue of non-empowerment of the user also exists in the themes report; in the design of the schedule; and also with the lack of fundamental items in the base view such as priority (and due dates). Basically in almost every part of the product.

Please give the user the ability to control their outcomes and let this product be as good as it should be. In the meantime, if/once we have developed a progress report that can cater for multiple projects, we will stop paying for this product as it provides little value - we're just using it for experimentation at the current time.

Suggest an answer

Log in or Join to answer
Community showcase
Josh Frank
Posted Dec 01, 2017 in Portfolio for Jira

Portfolio for Jira: Share your tips!

The Portfolio for Jira team wants to hear from you. Share your top tips for building a great Portfolio for Jira plan for a chance to win some Atlassian swag.  Do you structure your teams i...

558 views 6 8
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot