I have been playing around with Portfolio v 2.0, I am facing few issues, are they bugs or is it the way JIRA portfolio has been designed? Along with Epic I am using "Feature issue Type" at the same level of hierarchy underneath the Initiative issueType.
Hi Tarun, to move an existing story to another epic, switch to the stories hiearchy view (hierarchy switcher at the right above the table), find the story there, and use the "Epic" column to set a new parent. if that column is not visible, you might have to display it with the column selector. > we're working on improvements to make this easier, but this is how you can reach it right now in 2.0
regarding hierarchy / issue links: the parent/child relation is not mapping to the concept of issue links by design, but is stored separately (similar to the epic-story link on agile boards). it currently does not show up on the issue, but also for this we're prototyping solutions, potentially as a field similar to the "Epic Link" on the issue.
Hope this helps! Best, Martin (PM for Portfolio @ Atlassian )
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs