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've been using Jira Advanced Roadmaps for a month or two now, but mainly for organizing a view across projects into initiatives and epics, and hypothetical scheduling. I'm using the new interface.
I'd like to now use the auto-schedule feature to see what proposed timelines will look like. I'm running in to a problem, namely that auto-schedule is always resetting the duration for any ticket to 1 day. I've tried setting
It's not clear to me from the documentation which values the auto-schedule uses in its algorithm, and which ones it will respect as given.
Any tips are welcome.
Hello @Patrick Wright ,
Thanks for reaching out. First you noted adjusting start and end dates as well as Target dates, there is a change in the new interface and it now uses only one type of date, and the scheduling in the auto scheduler will be based on date that yuou have set in the plans scheduling configuration.
See "Scheduling issues" for additional detail son the settings, but I recomend checking to verify that the date range you have selected lines up witht he one you are altering in the issues.
Ultimately the Auto Scheduler (Detailed here) should be taking into account:
The program's schedule is derived from the dates, sprints, and releases of each plan in the program.
When auto-scheduling the issues in a plan, several factors are considered:
- how your teams work, i.e. in sprint iterations (Scrum), or in a continuous flow of daily tasks (Kanban)
- for Scrum teams, the sprint assignments of the issues in the plan
- the sequence of issues, based on start and end release dates
- the ranking of the issues in the plan
- the dependencies between issues in the plan
- the estimates of the issues in the plan
- the number of members in your team, which determines how much work can be completed in parallel
I recomend running through t he items listed and checking if any of the items line up with a data point that would impact the schedule for the items being reset to 1 day.