[#XPR-149] Accuracy view, iteration status original task estimate does not include Carrier Over tasks

xplanner

Accuracy view, iteration status original task estimate does not include Carrier Over tasks

Created: 26/Oct/05 10:39 AM Updated: 07/Dec/05 02:51 AM

Component/s:

None

Affects Version/s:

0.7

Fix Version/s:

0.7

Time Tracking:

Original Estimate:

4 hours

Remaining Estimate:

4 hours

Time Spent:

Not Specified

Issue Links:

Related

This issue relates to:

~~XPR-118~~ Accuracy view - Some stories have neither Original nor Current estimate

Description

« Hide

Make sure that all calculations in the iteration status table include carry over tasks/stories.
For the purpose of the calculation carried over are considered planned tasks/stories:
estimated = carried over estimated + planned estimated

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Tomasz Siwiec - 29/Nov/05 07:39 AM

It looks like the carried over task estimated hours are added to planned task estimated hours to calculate original task hours in Iteration Status table.
However, in case iteration is started original estimated hours value is saved in DB and adding new tasks doesn't change that value. Even if you add a task and change its disposition to Carried Over or Planned it will not be taken into account - that's ok I think. Is here any trick that I haven't got?

[ Permlink | « Hide ]

Jacques Morel - 29/Nov/05 12:31 PM

Good catch. This isn't ok. The carried over state is only a reminder that the story was started in a previous iteration.
From a calculation perspective it should be considered as a new task: When the story/task is carried over, the original task/story estimate should be wiped out