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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We have 10+ engineering teams around our core SaaS products - in today's world when we look ahead to 2019 and 2020 for roadmap planning, we end up with a lot of work in spreadsheets and elsewhere to map out how we'll tackle work.
My hope has been that Portfolio 2.1 would help us put that all in one place. However, as we set up Portfolio, I'm finding that it only really helps with planning around extremely well defined project - you need your epic to be populated with stories and story points put on them all so JIRA can understand scope, otherwise (if no stories yet for example), Portfolio pretends the epic doesn't exist... doesn't include it in the schedule at all.
Am I missing something, or is this really a pretty short-sighted tool for the current work and immediate future?
You are correct, the current Cloud version is essentially useless unless you know exactly how long your work is going to take and all of what it is far in advance. There is absolutely NO flexibility with the tool, it's their way or the highway