Project Planner - iPhone version of our the most popular application.
FS#110 - Behaviour of "Summary Start" and "Summary End" buttons is unpredictable
Attached to Project:
Project Planner iPhone
Opened by Mike (Feathers) - 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 Wednesday, 14 November 2012, 14:41 GMT+2
Opened by Mike (Feathers) - 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 Wednesday, 14 November 2012, 14:41 GMT+2
|
DetailsSelecting what I call the "Summary Start" and "Summary End" buttons sometimes adjusts the start and end positions of the assocated Summary Task but at other times it changes another existing task into a summary task (and loses all of its associated data in the process).
I know the manual hasn't been published for this button yet but if it is going to delete data that has already been entered then I believe it needs to identify the data that is going to be affected and give the user a chance to say "No" if it wasn't what he wanted to do. Specific example: I had: Summary task Task 1 Task 2 (with a dependency on Task 1) I entered a new Task 3 and selected the "Summary Start" button. The result was that the Summary Task was not adjusted but Task 1 was changed into a summary task. |
This task depends upon