Project Planner for OSX - OSX version of Project Planner and Project Planner HD
FS#128 - Project Planner updates predecessors too slowly
Attached to Project:
Project Planner for OSX
Opened by Valentin Mladenov (dragolcho) - Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /home/users/peritum/public_html/tracker/includes/class.tpl.php on line 594 Warning: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /home/users/peritum/public_html/tracker/includes/class.tpl.php on line 613 Monday, 11 February 2013, 11:26 GMT+2
Opened by Valentin Mladenov (dragolcho) - Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /home/users/peritum/public_html/tracker/includes/class.tpl.php on line 594 Warning: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /home/users/peritum/public_html/tracker/includes/class.tpl.php on line 613 Monday, 11 February 2013, 11:26 GMT+2
|
DetailsHere is my use case:
1. I create Resource 1 2. I create Task 1 (Start time 18.02, Duration Days, Allocation Resource 1) 3. I create Task 2 (Add Task 1 as Predecessor, Duration 2 days, Leave other fields untouched including Start time) 4. After a while (a few seconds up to a few minutes) Task 2 is correctly scheduled to start AFTER Task 1 Other observations: 1. Sometimes it takes a lot of time for the Task 2 to be rescheduled |
This task depends upon