How to import JIRA Issue relations into Portfolio?

[Alexander Haag]

We try to replace a requirements tool, and Portfolio seems to match quite all needs which exist.

We have the Issue-Types with the same naming, but still this matching does not really work always.

Issue-Types (Epic, Story) ==> Portfolio (Epic, Story)

But there is one Requirement which is not achievable, that the JIRA-Issue relations are imported dynamically.

Is it possible to import JIRA-Issues into Portfolio with the Links "relates To" and "is blocked"?

If not, is there a way hooking into the "import" process and implement the requirement?

[Martin Suntinger · Accepted solution]

Hi Alexander, currently this is not possible, the issue import does not map issue links to dependencies in Portfolio - only the other direction is possible when creating dependencies in Portfolio they can be set as issue links onto the JIRA issues. 

That being said, we're working on a new integration model which will allow to load issue links dynamically and specify which issue relation types are relevant for Portfolio and should be interpreted as dependencies. A beta is coming soon, you might also be interested in my talk at the Atlassian Summit - talking point #3 (from min. 12:30) focuses on the integration model, though it is quite high level http://summit.atlassian.com/videos/featured/portfolio-for-jira it gives you an idea where we're going. 

[Matthew Jagiello]

You can create Story-Epic links directly in Portfolio, not sure about the standard links (such as relates to or is blocked). Another project portfolio management plugin, BigPicture, certainly allows you to do so with proper links mapping.