Portfolio for Jira next-gen support
Error rendering macro 'viewport-redirect'
null
Portfolio for Jira doesn’t support next-gen projects.
We don’t encourage people to use Portfolio with next-gen. However, if you still want to use Portfolio with your next-gen projects, there are a few things that won’t work at all:
Parent-child relationship: If you try to save a story to epic relationship in Portfolio, it won’t be properly stored in next-gen.
Sprints: Portfolio doesn’t load sprints coming from next-gen boards.
Assigning issues from Portfolio won’t work in next-gen boards.
Story point estimates: You won’t be able to commit story point estimates to Jira if you’re issues are next-gen.
Time tracking: You can still set time estimates in Portfolio but they won’t show in Jira.
Issue type mapping: You next-gen project issue type will all implicitly be mapped to the story hierarchy level unless you fix that in the Portfolio hierarchy configuration.
Target dates: You can use target dates in Portfolio, however, if you commit them to Jira, the changes won’t be reflected in your nex-gen roadmap.