Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

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.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

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!

Leaderboard

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.

Atlassian Community about banner
4,551,961
Community Members
 
Community Events
184
Community Groups

Jira Advance Roadmaps Auto-schedule always resets duration to 1 day

Hi,

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

  • start and due date
  • estimation (d)
  • target start and target end
  • duration by dragging the timeline

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.

Thanks!

1 answer

0 votes
Earl McCutcheon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 25, 2020

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.

And

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.

Regards,
Earl

Hi Earl,

thanks for the detailed response. I'll set aside time this week to try and experiment with the project settings to see if I can figure out what's causing this 1-day estimation. I'll report back once I have some findings.

 

Thanks!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events