Moving unstarted task adds 1 millisecond
Hi,
If we move an unstarted task to a new iteration with "Continue Work" 1 millisecond is added to the estimated time. Does anyone else see this? |
4 answers
|
Meant to add this is the 2.0.0.2 client
|
Meant to add this is the 2.0.0.2 client My RTC installation (2.0.0.2 iFix 3) is also behaving this way. The extra millisecond started showing up when we migrated from one physical machine to another. Is there some setting that we can tweak to correct this? This might be minor if you just think of it as "only one extra millisecond", but the extra text that shows up in the planning view causes the estimate column to be wider than it needs to be and creates a cluttered view. The tasks then get reset to the original estimate and everyone subscribed to the work item gets another notification email. I'd like to understand what causes this behavior and anything that could be done about it if there are any suggestions. Thanks, Jim |
I agree this sounds like a defect to add the millisecond, or at least an odd behavior.
Can someone from the RTC dev team comment? It happens to me when I do a "Continue work in " action. |
ditto,
I heard the developer did a "I did a "Continue in Nov. 2010" action on it, rather than "plan for Nov. 2010"" I have the same behavior on my ticket as well, this should be defect unless someone can explain why this happens. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.