Details
-
Suggestion
-
Resolution: Fixed
-
4,030
-
Description
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.
Attachments
Issue Links
- duplicates
-
- Closed
- is duplicated by
-
- Closed
-
- Closed
- relates to
-
- Closed
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-