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.
To see this feature in action check out our recent dependencies demo here: https://www.youtube.com/watch?v=eQu5VsUqyZA Keeping on top of your dependencies is a key part of ensuring project success....
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