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

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? 

1 answer

0 vote
Steven Behnke Community Champion Jan 05, 2016

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

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published yesterday in Confluence

Three common content challenges + how to manage them

An efficient enterprise content management system, or ECM, is a must-have for companies that create work online (cough   cough, all companies). If content calendars, marketing plans, and bu...

69 views 0 4
Read article

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