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.
Understanding the auto-scheduling in 3.x
We recently upgraded from 2. 13 to 3.18, and the first thing I'm missing is the 'scheduling factors' from v2.x, explaining why an epic is not scheduled earlier.
As an example below, I have epics that are only scheduled to start within >6 months from now (most of them without dependencies), and would like to understand why they are not scheduled earlier (or what I need to change to schedule them earlier).
If the 'sheduling factors' are not available in 3.x, I'd be interested in hearing about the plans of adding this in the future + a description of the different parameters that are taken into account by the scheduling algorithm (+hierarchy of these parameters).
