Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support backward scheduling #468

Open
GoogleCodeExporter opened this issue Jun 28, 2015 · 9 comments

Comments

Projects
None yet
4 participants
@GoogleCodeExporter
Copy link

commented Jun 28, 2015

Very often people schedule their tasks  from the due date or required-by date 
to determine the start date and/or any changes in capacity required.

Original issue reported on code.google.com by dbarashev on 26 Mar 2012 at 6:42

@GoogleCodeExporter

This comment has been minimized.

Copy link
Author

commented Jun 28, 2015

Has this issue ben implemented?
Thanks for the help,
C.

Original comment by claudebe...@gmail.com on 23 Nov 2012 at 12:28

@GoogleCodeExporter

This comment has been minimized.

Copy link
Author

commented Jun 28, 2015

Until the status of the issue is not set to 'Fixed' the issue is not (yet) 
implemented.
So in this case: no, it's not implemented

Original comment by maarten....@gmail.com on 23 Nov 2012 at 8:54

@GoogleCodeExporter

This comment has been minimized.

Copy link
Author

commented Jun 28, 2015

Issue 735 has been merged into this issue.

Original comment by dbarashev on 31 Jan 2013 at 2:13

@GoogleCodeExporter

This comment has been minimized.

Copy link
Author

commented Jun 28, 2015

Has this been implemented in 2.6.1 ? (Probably not because still open)

Original comment by ignacelo...@gmail.com on 11 Apr 2013 at 12:32

@RitaPop

This comment has been minimized.

Copy link

commented Nov 10, 2015

I am already using the entered end date and duration with the calculated start date option to attempt this. But after applying dependencies, of course the end date pushed out again. So, I was then looking for some way to make at least the end milestone in a string of tasks have a fixed end date, and push all tasks backward from there, even if it has to throw warnings or errors or something. Are these ideas included in #468?

@dbarashev

This comment has been minimized.

Copy link
Contributor

commented Nov 10, 2015

@RitaPop you can try using Start-Finish dependencies instead of Finish-Start. This will look a little bit crazy, but it does work, just as if you draw a chart right-to-left.

Yes, dependencies working backwards are assumed in this issue.

@RitaPop

This comment has been minimized.

Copy link

commented Nov 11, 2015

Start-Finish on preceding tasks and strong link hardness on the dependency cleaned this up quite well. I can work with this.

@MSpaepen

This comment has been minimized.

Copy link

commented Sep 26, 2016

Would it be possible to define the default "Predecessor Type" (eg: Start-Finish).
I know you can define the hardness "Strong" or "Rubber" as default, but I would like to define the Type as well to use the above "trick" to use hard deadlines.
Second Remark, if you use "Rubber Hardness" you can still drag the curent task exceding the predecessing task. This should be the oposite and there should be the ability to drag it further in the past... (so you have more spare time to accomplish the current task). Please ask if this explanation is not clear.

@dbarashev

This comment has been minimized.

Copy link
Contributor

commented Sep 26, 2016

Default dependency type is hardcoded, sorry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.