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?
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.
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot