You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.