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'm experimenting with Structure Gantt for our team and, while it's looking pretty good, it isn't handling allocation like I expect. I set up a "Teams" field like the instructions said and have configured it to have 5 Units capacity and added it to our project's epics. Some of the issues are already started, so I've adjusted their start and estimates to accommodate Structure automation:
The result is overallocation of the team with a lower ranked issue (this has a Sort by Rank applied):
IOS-6797 should be scheduled after IOS-4081 when the team load drops? Why is it scheduled to start on Monday, the "start" of this Structure/schedule?
Hello @Janene Pappas ,
David from ALM Works here.
Based on what you have described, you will want to review this documentation regarding Resource Leveling.
From the screenshots I gather you are using some combination of Auto and Manual scheduling. We have some documentation that goes over the key behaviors specific to Stucture.Gantt here, that I believe will be very helpful as you are experimenting.