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

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!

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

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?

 

 

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

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

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"

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...

557 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