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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Cannot reschedule issues in Advanced Roadmap

I'm trying to create a roadmap for our product and one need that we require is that when an epic was delayed and it's period extended all dependencies should move forward in time to accommodate for the change. I made sure all settings for rescheduling issues are active and I use the auto-scheduler but nothing happens.

Here's an example

Screen Recording 2020-11-27 at 09.36.53.gif

2 answers

Hi @Daniel Tranca,

Could you have a look into your plan settings by clicking the cog wheel next to the plan's title.

On the Scheduling page, have a look at the setting for dependencies and verify if it is set to sequential:

Screenshot 2020-11-27 at 11.27.22.png 

Hi @Walter Buggenhout _ACA IT_ ,

 

Thank you very much for your quick reply. It's already set on Sequential.

That's not it then. The calculations used are a complex matter, taking a lot of factors into account. Dependencies are just one of them, so there will be something else determining the behaviour.

Could you check if changing the order of issues has an impact? Just drag KW-1 below KW-6.

In case re-ranking does not fix the issue yet, have a look at this page in the documentation - it explains a lot about the scheduling features.

A small extract, which may be key to analyse what is going on in your case:

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

As you can see as per my two previous hints, we were just starting to climb the ladder of influencing factors. ;-)

If you can't seem to get auto-scheduling to get it right, you can still adjust manually, right?

Like Earl McCutcheon likes this

 

Hi @Walter Buggenhout _ACA IT_ 

I did check that documentation before but none of those factors should be affecting my timeline. 

Hey @Daniel Tranca,

I am 100% sure they do - computers are always right, you know ;-). But it is true that we haven't found which one it is yet.

As these are Epics which I can see are collapsed in the roadmap currently, what scheduling information do you see from the underlying issues? Either fixed or auto-calculated. 

I haven't added any scheduling information to any of the Stories inside, since we want to use this road map for the next year, but don't want to estimate each story now. We would only like to estimate(roughly) the epics and build the roadmap based on that.

0 votes

Hello @Daniel Tranca ,

Taking a look at your setup I believe the issue is the sequence of issues, based on the start and end release dates as covered in the "Auto-scheduling issues" documentation under the section "Auto-scheduling in the improved interface" noting the factors the calculations are based on:

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

The auto-schedule function primarily looks to adjust either empty or all values when looking at "Sprints, teams, and releases" fields directly, as stated in the dropdown selector for the feature, there are other factors that will be populated when empty as covered in the list from the documentation but when a date is manually set for start and end dates the auto-scheduler will not try to adjust them but rather flag errors in the dependencies or list negative lead time as you are seeing.

If you delete the start and end date the auto-schedule should then be able to look at those values without having the additional constraint of being set manually then set the dates schedule accordingly based on the other factors.

Regards,
Earl

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM Trial
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...

7,120 views 8 28
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you