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

Fixed start date requirement in auto-scheduling Edited

It is very important to be able to specify a start date on an issue as a fixed constraint when using auto-scheduling. Everyone needs this, I guarantee it. Advanced Roadmaps auto-schedule does not seem to be able to respect both this and issue dependencies at the same time.

 

Example: a plan with just two tasks. Make the first one block the 2nd. (Awesome ability to specify and visualize this in the Advanced Roadmaps UI - love it!) But the first one cannot start until day X, because the world says so. Perhaps it's an externally-driven deadline, perhaps internal that can't be represented in Jira. Either way, the schedule won't be useful without retaining such a constraint.

 

If you enter an estimate for both issues and auto-schedule, the start date will be overridden. Does not seem to matter whether Target Start or Start Date is specified, or which one of the two is configured for visualization on the roadmap. The issue dependencies, however, will be respected, with the 2nd task starting after the first. But the start date of the first will be overridden to start on the current day, and there is no way to constrain this.

 

There is handling of unestimated issues. One idea would be to remove the estimate for the 1st issue, since this doc says that unestimated issues will not have their dates changed. So indeed, removing the estimate allows the dates to remain fixed, but then the scheduler does not respect the "blocks" dependency, and will schedule the blocked issue to start right away, on the current date. This seems like a straightforward bug in the scheduling algorithm. But really, it should respect the "start date" field as a fixed constraint when the issue has an estimate.

 

To make this crystal clear, here are demo screenshots.

 

Simplified team setup to illustrate scheduling problem:

team_setup.jpg

 

Issue setup with estimates, and a fixed start date requirement (here June 1; as I write today is May 20):

FireShot Capture 060 - Schedule fail plan - Portfolio for Jira - Jira - climatecentral.atlassian.net.jpg

Failure mode - moves target start to current date. But not only that, shifts the entire dependency chain ahead.

oops1.jpgAnd it should move the dependency chain ahead - you want it to schedule things as soon as possible. But this magnifies the severity of this lack of respect for a fixed date, because when it schedules the entire dependency chain ahead of where it would be given the 1st issue fixed start, none of the schedule estimates for dependencies can be used. Does not matter if we switch to using Start Date as the roadmap visualization. I get that this redesigned product is meant to offer full control of the roadmap, so that one can manually make adjustments when not satisfied with the calculated schedule. That's great! But it doesn't work here, because if you have a long dependency chain, dragging the first issue is blocked, it does not shift the entire chain forward. It's nearly impossible to drag a big dependency sequence around while preserving it.

 

Try using an unestimated issue so that the scheduler won't change the dates:

unestimated_setup.jpg

Failure mode:

oops2.jpg

Oops! This just seems to be a bug, rather than a sorely needed missing feature as may be in the 1st case. I can't imagine some sort of design constraint would require it to behave this way to fail to account for the blocks relationship here.

 

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
Community showcase
Published in Advanced Roadmaps

3 short videos to help you get started with Advanced Roadmaps

Hi community, I’m Roi, a product manager working on Advanced Roadmaps for Jira. While Advanced Roadmaps is a powerful tool to plan and track work at scale, we know it can be challenging to get star...

6,556 views 25 18
Read article

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