-
Suggestion
-
Resolution: Fixed
-
4,030
-
Actually only the EPICs from JIRA Software company managed projects are recognised and supported as EPICs by Portfolio.
Epics coming from the Team-managed (aka Next-Gen/Simplified/Independent/Agility) project's feature are not recognised as EPICs and are listed as "standard" tasks within the Portfolio plan's backlog without possibility to use them for dependancies.
Workaround:
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.
- duplicates
-
JRACLOUD-88871 Ability to view next-gen projects in Advanced Roadmaps
- Closed
- is duplicated by
-
JRACLOUD-89064 Adding support for Advanced Roadmaps in next-gen projects
- Closed
-
JRACLOUD-89178 As a Portfolio for Jira user, I want Portfolio to support next-gen projects
- Closed
- relates to
-
JRACLOUD-88746 Support cross-project parenting of TMP Epics across JSW
- Closed
- was cloned as
-
JRACLOUD-87947 Add support for EPICs from Team Managed projects into Advanced Roadmaps
- Gathering Interest
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
Hello everyone,
We greatly appreciate your feedback on our first milestone for supporting team-managed projects in Advanced Roadmaps. Your input is invaluable and helps us determine our next steps. As a result, we're now focusing on supporting cross-project parenting of TMP issues across JSW for our next milestone. To stay updated on this issue, please vote, watch, or comment. We aim to deliver this added value to you soon.
As we've now released our first milestone to all customers, we'll be closing this suggestion. However, we welcome additional feedback about your planning experience with team-managed projects in Advanced Roadmaps. Please join our Community group or sign up to chat with us directly via this Calendly schedule.
Cheers,
Emma