<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/1.2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>ProjectLoad Blog Comments</title>
	<link>http://blog.projectload.com</link>
	<description>Your online answer to organizing and tracking work</description>
	<language>en</language>
	<pubDate>Thu, 11 Mar 2010 00:26:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.2.2</generator>

	<item>
		<title>by: Keith</title>
		<link>http://blog.projectload.com/archives/2005/03/01/forecasting-your-work/#comments</link>
		<pubDate>Mon, 06 Jun 2005 09:36:48 -0400</pubDate>
		<guid isPermaLink="false">843:27@http://blog.projectload.com</guid>
					<description>	Thanks for the feedback Reena!  Unfortunately there is no easy way to recover the data.  The system assumes that if the user types a number in the &amp;#8216;hours left&amp;#8217; column then he or she is changing the estimated hours.  There is simply no way for the system to know the user didn&amp;#8217;t intend the hours to apply in the column they were typed in.  One other user did report this same problem a few months ago and we changed the system to always keep the column headings on the screen and to display the background color of the &amp;#8216;hours today&amp;#8217; input field as a light blue so it stands out.
	On activities a user has marked as &amp;#8220;do not forecast&quot;, there is really no reason to change the estimated fields.  We are always looking for ways to make ProjectLoad easier to use, so we have changed all timesheets to make the &amp;#8220;Target Date&amp;#8221; and &amp;#8220;Hours Left&amp;#8221; columns &amp;#8220;read only&amp;#8221; for activities the user does not wish to forecast.  Hopefully this will prevent users from making this mistake in the future and also help people recognize when they have an activity marked as &amp;#8220;do not forecast&quot;.
	Thanks for helping us to continue improving the system!

</description>
		<content:encoded><![CDATA[	<p>Thanks for the feedback Reena!  Unfortunately there is no easy way to recover the data.  The system assumes that if the user types a number in the &#8216;hours left&#8217; column then he or she is changing the estimated hours.  There is simply no way for the system to know the user didn&#8217;t intend the hours to apply in the column they were typed in.  One other user did report this same problem a few months ago and we changed the system to always keep the column headings on the screen and to display the background color of the &#8216;hours today&#8217; input field as a light blue so it stands out.</p>
	<p>On activities a user has marked as &#8220;do not forecast", there is really no reason to change the estimated fields.  We are always looking for ways to make ProjectLoad easier to use, so we have changed all timesheets to make the &#8220;Target Date&#8221; and &#8220;Hours Left&#8221; columns &#8220;read only&#8221; for activities the user does not wish to forecast.  Hopefully this will prevent users from making this mistake in the future and also help people recognize when they have an activity marked as &#8220;do not forecast".</p>
	<p>Thanks for helping us to continue improving the system!
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Reena Chaba</title>
		<link>http://blog.projectload.com/archives/2005/03/01/forecasting-your-work/#comments</link>
		<pubDate>Fri, 03 Jun 2005 10:29:23 -0400</pubDate>
		<guid isPermaLink="false">724:27@http://blog.projectload.com</guid>
					<description>	Keith,
If an activity is set to the &amp;#8216;do not forecast&amp;#8217; option, and a user enters data in the &amp;#8216;hours left&amp;#8217; column instead of the &amp;#8216;hours today&amp;#8217; column, is there an easy way for the administrator to resolve this? I understand that I will need to reset the estimate back to 0 but do we lose the data the user entered in the &amp;#8216;hours left&amp;#8217; column altogether?

</description>
		<content:encoded><![CDATA[	<p>Keith,<br />
If an activity is set to the &#8216;do not forecast&#8217; option, and a user enters data in the &#8216;hours left&#8217; column instead of the &#8216;hours today&#8217; column, is there an easy way for the administrator to resolve this? I understand that I will need to reset the estimate back to 0 but do we lose the data the user entered in the &#8216;hours left&#8217; column altogether?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Karlene Coyan</title>
		<link>http://blog.projectload.com/archives/2005/04/25/action-buttons-in-lists-re-organized/#comments</link>
		<pubDate>Wed, 11 May 2005 16:09:01 -0400</pubDate>
		<guid isPermaLink="false">653:30@http://blog.projectload.com</guid>
					<description>	Thank you for changing this so quickly.

</description>
		<content:encoded><![CDATA[	<p>Thank you for changing this so quickly.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jonny Roller</title>
		<link>http://blog.projectload.com/archives/2005/04/25/action-buttons-in-lists-re-organized/#comments</link>
		<pubDate>Thu, 05 May 2005 05:53:48 -0400</pubDate>
		<guid isPermaLink="false">632:30@http://blog.projectload.com</guid>
					<description>	Thanks for your feedback! We discussed changing the series of buttons into a drop-down list for quite some time. We quickly came to the realization that adding more functions to the system would cause the page to become much too wide. So we&amp;#8217;ve opted to go for a menu-like approach so that we can add more actions without changing the layout of the page.  We&amp;#8217;ll be rolling out one of those new actions soon&amp;#8230; stay tuned!
	Your point about the action list switching back to the first selection in the menu is a valid one.  This was done so that if the action caused a new window to open, the action list would be automatically reset so that you could choose another action easily.  However, as we discussed your comment it occurred to us that we only need to reset the action list if you are indeed causing a new window to appear (this is something we can detect).  We can also make the action list reset itself a few seconds after the new window opens as well.  With this change that we just rolled out, using the action lists should be a little easier.
	Thanks again for your comments!

</description>
		<content:encoded><![CDATA[	<p>Thanks for your feedback! We discussed changing the series of buttons into a drop-down list for quite some time. We quickly came to the realization that adding more functions to the system would cause the page to become much too wide. So we&#8217;ve opted to go for a menu-like approach so that we can add more actions without changing the layout of the page.  We&#8217;ll be rolling out one of those new actions soon&#8230; stay tuned!</p>
	<p>Your point about the action list switching back to the first selection in the menu is a valid one.  This was done so that if the action caused a new window to open, the action list would be automatically reset so that you could choose another action easily.  However, as we discussed your comment it occurred to us that we only need to reset the action list if you are indeed causing a new window to appear (this is something we can detect).  We can also make the action list reset itself a few seconds after the new window opens as well.  With this change that we just rolled out, using the action lists should be a little easier.</p>
	<p>Thanks again for your comments!
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Karlene Coyan</title>
		<link>http://blog.projectload.com/archives/2005/04/25/action-buttons-in-lists-re-organized/#comments</link>
		<pubDate>Wed, 04 May 2005 15:03:29 -0400</pubDate>
		<guid isPermaLink="false">622:30@http://blog.projectload.com</guid>
					<description>	I don&amp;#8217;t really like the drop down list. It would help if it would display the action you selected while waiting for the next screen.

</description>
		<content:encoded><![CDATA[	<p>I don&#8217;t really like the drop down list. It would help if it would display the action you selected while waiting for the next screen.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
