I am working on rollout Portfolio and supporting the rollout.
I am asked several times on why the hierarchy in portfolio (phases, themes, epics) are not ordered on how it was originally setup.
I try to explain how portfolio schedules using backlog, Release/FixVersion, sprints, etc.
It would be great to have a good document to point people to for current UX and new UX.
Hello @Scott Torbert
Indeed the auto-scheduling in portfolio can get confusing for lot of users.
Here's an KB article about it - https://confluence.atlassian.com/jiraportfolioserver0224/scheduling-behavior-967311554.html
Also, the scheduling factors are listed on the issue itself on the portfolio.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.