I would like to better understand how a ticket's estimated hours is split over sprints when the ticket spans into two projected or future sprints.
I have a plan with only one ticket with hours estimated for simplicity. It has 10d in its Time Remaining estimate and my future sprint is set to 5d and lasts a week.
If on the timeline I make that ticket start and end in that future sprints week it correctly shows 200% capacity. Planning 10d in a sprint of 5d is expected and all is behaving well.


When i make that ticket last two sprints I would expect both sprints to now be at 100% capacity - each with 5d in them. But instead it splits it in some manner I cannot understand. Why does it split them in 2.5d in one sprint and 7.5d in the second sprint?



Should it not be 5d in one and 5d in the next?