It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Portfolio for Jira: How do I get my next Gen projects to show up properly in Portfolio for Jira?

I added a next Gen project to Portfolio Plan and it does not show up When I am viewing the epics.  I created a separate plan with only that new Next Gen Scrum Project, and it imported the issues, but it considers an epic the same as a task, so none of my work is rolling up into epics to give me the Gantt view.  Has anyone had any luck with the Next Gen Scrum projects and Portfolio for Jira?

4 answers

Hello ! Same problem, and the story points aren't linked too

@André Aubin  I got a response from Atlassian. 

"This is a known limitation on Portfolio that can't map the Next-Gen issue types as they have some different set of configurations from the classic project, that's why when using a Next-Gen as issue source for Portfolio you don't see the epic at the Scope table when using the hierarchy for Epics."

They have a ticket open to extend the Portfolio for Jira to Next-Gen projects.  You can vote on it to help this feature move forward.  

https://jira.atlassian.com/browse/JPOCLOUD-2652


Like # people like this

Same Boat! Feel very helpless.

Deal break. Cannot and wont use NexGen projects if portfolio does not support them.

Hi @Amy Garcia any update. We are almost a year ahead ......?

@Floor Tuinstra 

The issue is still open.
https://jira.atlassian.com/browse/JPOCLOUD-2652

Another related issue that may solve the problem, the new Next Gen Projects have the nice Roadmap Gantt view.  If Jira would add the ability to customize the filter to show multiple projects(like they do for the original Jira projects), This Roadmap feature could replace Portfolio.  That ticket is here to add the ability to configure filters for next-gen projects:
https://jira.atlassian.com/browse/JSWCLOUD-17444

Hi @Amy Garcia  thanks for the quick reply and answer. Unfortunately this only works if you have a stand-alone project.

If you want to combine boards from multiple teams to see where they works on and do an analysis this Roadmap functionality can't be used unless you have a solution for this?

This might be of help for simple scenarios. Portfolio allows to manage teams, skills, velocity and cross-project planning, which is more than a simple roadmap.

Like Floor Tuinstra likes this

@Floor Tuinstra Yes that is correct, it's not possible in Next Gen.  That's why I linked the ticket  to add the ability to configure filters(to show multiple projects) for next-gen:
https://jira.atlassian.com/browse/JSWCLOUD-17444

Atlassian did release a new version of Portfolio, but it is only available for the server versions not cloud, and I do not know if Portfolio 3.0 is linked with Next Gen projects or not:
https://community.atlassian.com/t5/Portfolio-for-Jira-articles/Portfolio-for-Jira-3-0-is-here/ba-p/1043376

The only information I have seen about integrating Portfolio with Next Gen projects is on this ticket:

https://jira.atlassian.com/browse/JPOCLOUD-2652

This might be of help for simple scenarios. Portfolio allows to manage teams, skills, velocity and cross-project planning, which is more than a simple roadmap.

0 votes
Danny Community Leader Apr 21, 2020

Thought I should add a reference to the documented limitations of using Portfolio for Jira with Next Gen projects.

  • 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 next-gen roadmap.

So what is your recommendation to calculate the team capacity on the next gene? we established the user story points- Fabbinici method- we have 3 members of the team full time in 3 different projects and one team member to fix ad hoc and one Support. how we can calculate the capacity of the team during the sprint?

Like crouhana likes this
Danny Community Leader May 16, 2020

Hello @Mona

My suggestion would be to transfer the project to a Jira Classic Project type. You can either use Portfolio fully as your need for capacity planning is not met using a Next-Gen Jira Project type.

OR

You could use a marketplace add-on such as Sprint Capacity Planning though you would still need to transfer to a classic Jira project. 

This is not the answer you were hoping for as you are using Next-Gen. 

Thanks,

Danny

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Next-gen

Introducing manual board clearing for your next-gen Kanban board!

Hi Atlassian Community! My name is Ivan, and I’m a Product Manager on Jira Software Cloud. Project admins are spending hours a week tracking their team’s work on their boards. End users use the b...

48,757 views 11 15
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you