Why doesn't portfolio automatically match subtasks to their parent epics?

Thorbjørn Sigberg

This question is in reference to Atlassian Documentation: Importing existing issues to the backlog

We're testing out portfolio, and we already have tons of stuff in our backlog. I'm attempting to import existing issues, but even though they already are subtasks of an existing epic, portfolio doesn't seem to detect this, so I have to set all the epics manually on every issue. That is pretty cumbersome with ~400 issues. Why can't the portfolio import automatically set the linked parent epic as default epic? 

Steven F Behnke

Sub-Tasks cannot use the Epic Link field. Or do you mean you're doing Sub-Task level planning in JIRA Portfolio?

 

Perhaps you mean Stories?

If we're talking about main-level types, then you'd need to indicate during the import if you want to set them to a new epic or manually select which Epic you'd like them associated to.

image2016-1-5 17:7:16.png

image2016-1-5 17:7:50.png

image2016-1-5 17:7:50.png

image2016-1-5 17:7:16.png