Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Why are Issues are being imported without their parent Epics?

I am using the new Portfolio 2.0 on a JIRA cloud installation and I have a Plan set up.  I am trying to bring my epics in.  I am selecting the epics from the Plan-->Configure-->Issue Sources-->Edit Sources-->Confirm what's in Scope.  And a bunch of the Issues are coming in as "Issues without parent Epic" even though they have Epics within JIRA.  And a bunch of the Epics I've selected for inclusion aren't coming in at all.  These are not Epics that I have previously excluded from the Plan.

6 answers

So basically the very first answer explains it. Issues of a type 'Epic' should be present in your result set that you are using as a source for JIRA portfolio - be it coming for a board or from a filter. This effectively excludes any filters and boards that would  might have issues filter by 'having an Epic Link = SOMrTHING. You need to include another source, which would esentially say this explicitly: Epic Link = "YOUR EPIC"


i have the same problem but i dont understand your proposal lev.

My projects have EPIC and Stories.


And the EPICS  are not shown by Portfolio when i import it.

the are under featurea and safe epic - see here.


I have same issue with exactly same setup as your Ericka. Any luck ?

I was having the same issue.

It turns out that Portfolio won't bring in Epics at all if the Fix Version field is missing from the Epic screen in the project you are trying to add to your plan. The field can be empty, but it must be present.

This seems like a bug.

yes the fix version is there

the filter is the basic project = "xxx" ORDER BY Rank ASC

and the Epic Link is included in the columns displayed


Is there anything else this could be?  Is it because I never did a Commit from Portfolio before trying to reimport?

You have to be able to do that right?  What if you've excluded some Epics from your Plan and then decide you need to re-include them?



Yes - as Michael noted - double check your filter query utilized by the JIRA board included in your plan. 

We had a similar issue and were able to resolve it by changing the filter query on the JIRA board that was serving as our issue source. In JIRA we had a filter query that included:

issue type != epic

Removing this from the source board filter query resolved the issue. Hope that helps!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Confluence

An update on Confluence Cloud customer feedback – June 2022

Hi everyone, We’re always looking at how to improve Confluence and customer feedback plays an important role in making sure we're investing in the areas that will bring the most value to the most c...

124 views 1 3
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you