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 having trouble understanding the date auto schedule is populating in start date. For instance I have an issue that is already "In Review" status, but after clearing the dates of the story and the parent epic the auto populated date is still set to two weeks in the future.
I do have the Plan set up to Sequential Dependent
Is there any tooling to see why Plans suggested that date?
Jira Version: v8.8.0
Hi @Ollie Reid
Is your "In Review" status part of the "In Progress" status category? If so, the auto-scheduler is going to consider that there is work remaining and will schedule time based on the estimate assigned to it so that it can be completed.
Hi @Ollie Reid,
That's a fair point, I wasn't really justifying the behaviour but rather just trying to offer an explanation of why it's happening. Without having access to your plan I'm wondering if the scheduling algorithm is pushing the date back because of other work?
I don't think that the scheduling algorithm works on the understanding that if a piece of work has been started it absolutely has to be finished before scheduling other work.
However, I do agree that this is potentially confusing here. One of the differences in behaviour between auto-scheduling for Kanban and Scrum is that issues in the active sprint (i.e. those most likely to be in progress or about to be in progress) are not adjusted. With Kanban there's not really that same notion of a time-boxed iteration to lean on.
This is good feedback though and I appreciate you sharing it and I'll feed this back to the product management team.