Initiatives with next-gen projects
Asked by emmanuel.neret:

How can I create an extra level of hierarchy on top of Epic? i.e Initiatives or Themes like suggested [here](https://www.atlassian.com/agile/project-management/epics-stories-themes).

It seems like this is currently missing. I could bring everything one level down but Subtasks don't show up in the backlog or in boards...

Any idea how I could achieve this?

Thanks


Answers:
author: emmanuel.neret
body: Thanks Earl,

-Anything you recommend using in order to group epics under an umbrella?

-Is this something that on the backlog?

Emmanuel

comments: author: Earl McCutcheon
body: Hi [@emmanuel.neret](/t5/user/viewprofilepage/user-id/3848715) ,

I would recomend that if you are lookin to use the capabilities of Portfolio to its fullest check out the KB ["Migrate between next-gen and classic projects"](https://support.atlassian.com/jira-software-cloud/docs/migrate-between-next-gen-and-classic-projects/) and I would suggest converting the projects that you want to have in portfolio converted over to classic projects, But also make sure to read through the "Things to keep in mind if you migrate from next-gen to classic" section before doing so as a lot of the items will require a rebuild to weigh out the effort and impact of doing this.

The main conflicting points between Next-Gen and Classic projects in Portfolio, is that Portfolio for Jira is specifically aimed at managing an overlapping multi-project approach with shared elements, and Next-Gen projects are designed to be a simplified project type, to contain all elements within a single project isolated from other projects with project specific elements. As an example each Next-gen gets its own custom fields and issue types, but classic projects borrow from a global pool of these elements, and portfolio only looks at the global pool.

Additionally as the roadmap goes we do have things in the works, but at this time we do not have any ETA publicly available on new feature roll outs. However, Jason Wong, a lead Product Manager for Jira Cloud did hosted an *Ask me Anything* session back in October of 2018 so its a bit older but does answer a lot of question about next-gen and portfolio plans. A lot of interesting information about the roadmap and where the product is headed can be found here:

* [Jira Cloud 2.0 \| Ask me Anything with Jason Wong](https://community.atlassian.com/t5/Jira-questions/G-day-I-m-Jason-Wong-Lead-Product-Manager-for-Jira-Software/qaq-p/928598)

The feature request tracking the addition and support of Next-Gen Epics to Portfolio is being tracked here, add yourself as a watcher to get updates on the status:

* <https://jira.atlassian.com/browse/JPOCLOUD-2652>

Make sure to add your vote on the request to help us track the continued interest in this, Noting it already has a High Vote count, but every vote helps influence the priority for development as covered in the [Implementation of New Features Policy](https://confluence.atlassian.com/support/implementation-of-new-features-policy-201294576.html)

Regards,  
Earl


author: Earl McCutcheon
body: Hello [@emmanuel.neret](/t5/user/viewprofilepage/user-id/3848715) ,

Currently Next-Gen Projects do not support the parent child relation ship that allows the higher initiative levels in Portfolio for Jira.

This and other limitation of Portfolio are covered in the following KB article, but to use the functionality you will want to use Classic projects:

* [Portfolio for Jira next-gen support](https://confluence.atlassian.com/jiraportfoliocloud/portfolio-for-jira-next-gen-support-968663298.html)

Regards,  
Earl

comments: author: Jakub Kierszka
body: [@Earl McCutcheon](/t5/user/viewprofilepage/user-id/502460)   
This has been a huge challenge for thousands of your users.   
Having a configurable, multi-level hierarchy is a "must-have" for mature project management and a global requirement for every project management software. Users have have been asking this question and ones like it, since I started working with JIRA in 2009.

I have seen these dozens of requests sidelined with "there's a plugin" or "use Portfolio". Neither solution path adequately addresses the needs of PMs, SMs, and multi-team environments working on complex projects.

At an abstract level, expandable nested work breakdown structures (PMBOK WBS) are a must-have. I have come to understand it's an architectural shortcoming of JIRA, but I urge Atlassian to consider this, or you will recreate your Achilles Heel in your "next-gen" efforts. Wishing you and the team best of luck with this challenge.


Tags: advanced-roadmaps

initiative