Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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 new Jira Cloud Next-Gen projects?

Hi there,

Since Portfolio currently doesn't support Next-Gen projects and their issue types, do you plan to work on this and add this functionality? My company is trying to choose the right tool for project and portfolio management, and this will be extremely helpful to know since we do plan to use Next-Gen projects, and the new Roadmap feature.

1 answer

1 accepted

1 vote
Answer accepted

Hello Aleksandar,

Thank you for getting in touch with Atlassian Community!
Related to this limitation, we still don't have a date of when it will be implemented.
We've been tracking a feature request for this to make it available:
- https://jira.atlassian.com/browse/JPOCLOUD-2652
On the feature, there is a workaround that may help you:

Go to Portfolio's hierarchy configuration and map the Epic issue types coming from next-gen projects to the Epic level so Portfolio will properly recognise them.
STILL, once the mapping is done and the NextGen EPIC is mapped to the EPIC in the Portfolio's hierarchy settings:

  • The nextgen EPICs are recognised as EPIC and they can be created from within Portfolio and commit to the project, but there are other problems:
    • The dependencies are not imported from the project source into portfolio.
    • The dependencies creation and updates are not commit from Portfolio to project. This is causing discrepancies between the project and the portfolio plan and then the project needs to be updated manually to fit the commit plan.
    • The issues created with a dependency to an EPIC from Portfolio are not visible in the project backlog or board's views, they can be accessed as project's issues using the issuekey directly. This is not the case for the issues created without dependancy, they will appear in the project's backlog after the portfolio's plan change has been commit.


Please, click on vote and watch to receive updates about the feature.

Regards,
Angélica

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Advanced Roadmaps

3 short videos to help you get started with Advanced Roadmaps

Hi community, I’m Roi, a product manager working on Advanced Roadmaps for Jira. While Advanced Roadmaps is a powerful tool to plan and track work at scale, we know it can be challenging to get star...

6,516 views 25 18
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