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 use large place holder stories to account for initial estimates of our epics. As the teams break the epic down to stories, they pull points from these place holder stories. In Portfolio 2.0, we could set the number of members that could be considered to work on a story. This worked well as we assumed for these larger stories that more than one person could work on them at a time.
With Portfolio 3.0, it assumes only one person can work on these large stories so the timelines are obviously overextended. What is the intended way to plan for these larger epics before they get broken down in the new version of Portfolio? Is there a plan to bring back the setting to assume more than one person can work on a story?