What is the auto-schedule logic based on when clicked?

[David Markowski (DO NOT USE)]

I have been playing with the auto-schedule functionality and having a hard time figuring out the logic of the function from a backlog and a priority basis as it relates to epic priority and story priority and items in sprints vs items in backlogs and how it will choose items to put in a sprint.  Is there any definitive guide that can help with this? 

[Michael Andolfatto]

Hi @David Markowski (DO NOT USE) ,

The explicit algorithm isn't public, but auto-schedule takes (at least) the following into consideration:

• Issue ranks
• Associated releases
• Dependencies
• Sprint data
• Issue size/estimate + team capacity

You can read more about it here, but the gist is that you can choose between Advanced Roadmaps scheduling issues regardless of existing information (overwrite all values) or scheduling issues while making changes to only empty data (overwrite empty values only).

It then runs through the above information and tries to fit in as much as it can according first to rigid information (such as if an issue must belong to an upcoming release as noted in the ticket) followed by more fluid information (how high up an issue is positioned in the backlog for example)