Warning: mktime() [
function.mktime]: 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 'America/New_York' for 'EST/-5.0/no DST' instead in
/home/admin/www/wordpress/wp-includes/functions.php on line
30
Warning: date() [
function.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 'America/New_York' for 'EST/-5.0/no DST' instead in
/home/admin/www/wordpress/wp-includes/functions.php on line
36
Warning: date() [
function.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 'America/New_York' for 'EST/-5.0/no DST' instead in
/home/admin/www/wordpress/wp-includes/functions.php on line
37
Warning: mktime() [
function.mktime]: 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 'America/New_York' for 'EST/-5.0/no DST' instead in
/home/admin/www/wordpress/wp-includes/functions.php on line
30
Warning: date() [
function.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 'America/New_York' for 'EST/-5.0/no DST' instead in
/home/admin/www/wordpress/wp-includes/functions.php on line
36
Warning: date() [
function.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 'America/New_York' for 'EST/-5.0/no DST' instead in
/home/admin/www/wordpress/wp-includes/functions.php on line
37
Warning: mktime() [
function.mktime]: 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 'America/New_York' for 'EST/-5.0/no DST' instead in
/home/admin/www/wordpress/wp-includes/functions.php on line
30
Warning: date() [
function.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 'America/New_York' for 'EST/-5.0/no DST' instead in
/home/admin/www/wordpress/wp-includes/functions.php on line
36
Warning: date() [
function.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 'America/New_York' for 'EST/-5.0/no DST' instead in
/home/admin/www/wordpress/wp-includes/functions.php on line
37
6/11/2005
To encourage users to estimate their workload, the Daily Timesheets were changed in August 2004 to include columns for updating the “target date” and the “hours left” on each activity. On activities that had no estimates the extra input fields were blank and sometimes users accidentally input the daily hours in those columns instead of placing them in the “Today’s Hours” column. Since activities that are marked as “Do not forecast” seldom use estimates, the system has been changed to prevent a user from typing into the estimate columns on those activities. This should greatly reduce the chance that someone will type their daily hours in the estimate columns by mistake. If someone wishes to place estimates on an activity and yet flag it as “Do not forecast”, they can still do so by editing the activity.
Another benefit of this change will be to highlight those activities that are not being forecasted. When a user adds a new activity to the timesheet, if it defaults to “Do not forecast”, the user will be aware of this immediately and can correct it by editing the activity. Previous to this change, the user might type estimates into the timesheet and never realize they had not activated the forecasting option on the activity.