Earn badges and make progress
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
Next: Root
1 badge earned
Participate in fun challenges
Challenges come and go, but your rewards stay with you. Do more to earn more!
Gift kudos to your peers
What goes around comes around! Share the love by gifting kudos to your peers.
Rise up in the ranks
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Come for the products,
stay for the community
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Auto-schedule bugs - shifting teams, shrinking times, overbooking teams
I have a test Advanced Roadmap I am working with in preparation for creating roadmaps for all of our teams. I have 3 test projects with pristine issues. I've set up 4 JAR Kanban "teams" each with a weekly capacity of 40 hours. I have monthly releases for 1 of the projects. (This is what we have in our company.)
I've experimented and arrived at a schedule. When I then add a new task, lowest priority, 40 days estimate and auto-schedule, the preview shows Team 4. Team 4 is booked in a higher priority slot above so this would overbook Team 4. If I continue on and Accept the changes, the new Epic is instead assigned to Team 1, and overbooks Team 1 instead. This sequence is shown in the attached screenshots, colored by Team.
In my experiments, I've had the auto-schedule shrink the time to less than the estimate, but it consistently overbooks a team. Am I doing this wrong or are these bugs?
Added the new task. Preview shows Team 4:
Accepted changes, now assigned to Team 1:
This one with estimate of 50 days, overbooks Team 4 completely.
