Change of completion date of first element doesn ́t change following element?

  • 3
  • Idea
  • Updated 4 years ago
  • Implemented
In the task manager I can assign a start and finish date for a task.
When I assigned two elements the "end-end"-relationship, then the completion date of the first element is the start date of the second element.
And that runs automaticly. Very fine and run as i want. But when i change the first element and reduce the completion date the start date of the second element doesn ́t change backwards.....
Is that right? I don ́t understand that.... Is it a bug or feature?
Photo of SeaBear

SeaBear

  • 4 Posts
  • 0 Reply Likes

Posted 6 years ago

  • 3
Photo of Nigel Goult (Olympic & MIVAP)

Nigel Goult (Olympic & MIVAP)

  • 348 Posts
  • 135 Reply Likes
Seabear,

You are right in this....if you extend a finish date then all dependent tasks will advance in the timeline.but as you say, when you reduce the duration or complete the task early then the remianing tasks stay as they are and do not "shrink back" to contract the timeline.

I guess you will just have to wait until the start date arrives :-) or manually adjust them each time you complete a task early....

Regards

Nigel
Olympic Limited
OPTi-Addins FREE Addins for MindManager 2012
Photo of dawsonde

dawsonde

  • 2 Posts
  • 0 Reply Likes
We have a scheduling timeline that has 35 dependencies and this kills the entire software.  We thought that this could be the replacement for Office Project but not if this bug is in the system.
Dony
Photo of Nigel Goult (Olympic & MIVAP)

Nigel Goult (Olympic & MIVAP)

  • 348 Posts
  • 135 Reply Likes
If you are using, or upgrade to, MindManager 15 there is a new function/command - Remove Slack Time - that will allow you to do this so the problem has already been addressed.


Hope this helps.

HTH

Regards
Nigel

Olympic Limited
Extending Capability to Improve Application of Mindjet MindManager
Check out our latest MindManager add-ins: Topic Tracker - WordX
MAP for MindManager - Have you got the MAP? - Download Today
Photo of Michael Deutch

Michael Deutch, Official Rep

  • 438 Posts
  • 76 Reply Likes
Thanks, I marked this as implemented. 
Photo of Michael Deutch

Michael Deutch, Official Rep

  • 438 Posts
  • 76 Reply Likes
Seabear (like your name, by the way), I'm going to switch this over to be an idea so the community can weigh in and vote for this.

Thanks,
Michael
Photo of Jesse Wolfe

Jesse Wolfe

  • 2 Posts
  • 0 Reply Likes
Michael

I have seen a number of comments on this topic. Is there any plan or roadmap to add in a 'ASAP' feature for tasks that would allow them to move backwards in time when upstream tasks either finish early or have estimates change to a shorter timeframe.

I am a PMP and a professional services consultant for a big four firm and utilizing your software in a major project for our client. I would like to recommend adopting this software for my collegues for some of our complex projects due to its quick and easy set up and ability to rapidly decompose details in a visual manner. However the lack of a task start constraint (as soon as possible, as late as possible etc.) is a very limiting feature and will keep me from recommending this software as it creates an incredible amount of manual work on the PM's part. 

Happy to speak with your firm further on this topic.
Photo of Michael Deutch

Michael Deutch, Official Rep

  • 438 Posts
  • 76 Reply Likes
Thanks Jesse, I am pushing to add this feature. Your request adds further justification. Thanks for your input. 
Photo of Jesse Wolfe

Jesse Wolfe

  • 2 Posts
  • 0 Reply Likes
Seriously, this is a very basic feature of project dependency management and I don't understand how you need to push for this if you want to compete with prevailing PM tools. It simply is a dealbreaker. 
Photo of Alex Gooding

Alex Gooding, Champion

  • 886 Posts
  • 223 Reply Likes

I would like to second Jesse's comment that this is a basic and essential feature which is urgently needed in MindManager.

Even for maps of simple projects, bringing forward the completion date of an early task means you have to manually change all the later ones. This is laborious enough if say you have only a dozen tasks, but on anything bigger it is a nightmare.

I would suggest however that this feature be an additional option to the current finish-to-start dependency, rather than a replacement. So in other words you could have :

  • one finish-to-start dependency option as it is now, where the dependent task can start no sooner than the completion of the preceding task but can commence any time thereafter; and

  • a second finish to start option where the start date is fixed to the previous task's finish date and so will move backwards or forwards automatically with any adjustment to the duration and completion date of the earlier task.
Photo of dawsonde

dawsonde

  • 2 Posts
  • 0 Reply Likes
We want to implement this into our company's new workflow but this kills us.  This makes it impossible for us to make adjustments to our timeline!  This is a bug that has to be fixed asap or we cannot use this software in our system.
Photo of SeaBear

SeaBear

  • 4 Posts
  • 0 Reply Likes
Hej,
thanks for your answer. So i know that i am right in my doing so far....

Best
Rolf