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?
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