Feature #7545

Calculate the issue done ratio from estimated and spent time

Added by Luis Serrano Aranda almost 9 years ago. Updated almost 2 years ago.

Status:NewStart date:2011-02-04
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Issues
Target version:-
Resolution:

Description

It is possible to add an option to calculate automatically the done ratio from the relationship between the estimated hours and the real hours? (If we turn the percentage would be greater than 100)

Thanks and congratulations for your work


Related issues

Related to Redmine - Feature #12347: "Calculate the issue done ratio" per project configuration New
Related to Redmine - Feature #11999: Calculating issue done ratio based on "Estimated Time" an... New

History

#1 Updated by Adam Piotr ┼╗ochowski almost 9 years ago

Typically estimation does not match reality. Someone can estimate a task to take 5hours and is done within 15minutes. Other times after 10hours it still isn't half way complete.

If this were a feature, I would expect to have it turned off on my Redmine instances.

Kind regards

Adam ┼╗ochowski

#2 Updated by Marcus Fleuti over 7 years ago

We have the same request in #11999. See our description for the reason why this makes sense anyway. I totally understand Adams' argument. Although in some projects it totally makes sense to have the total issue done ration being calculated based on the spent time value. If Spent Time is greater than Estimated Time and the option to calculate the done ratio based upon these 2 values is turned on, the done ratio for a task should simply be set to 100%.

Perhaps, when using the option to calculate the done ratio based upon Estimated Time/Spent Time is enabled, the field Estimated Time should be renamed to Time Required or Lead Time. Then it again makes sense.

This is useful for projects where the customer pays for a certain amount of hours (in advance) and has the ability to check the status on the issue he payed for. Thus if Spent Time exceeeds Estimated Time the bar in the issue overview should become red or something to visualize that an issue is over the "limit".

#3 Updated by Samuel GABILLARD about 7 years ago

+1

#4 Updated by Gorka Siverio about 7 years ago

+1

We can add another field with the estimated remaining time and use it to calculate a more realistic done ratio. Something like this:

1) Starting:
Estimated Time: 8 h
Spent Time: 0 h
Remaining Time: 8 h
% done: 0 %

2) Halfway:
Estimated Time: 8 h
Spent Time: 4 h
Remaining Time: 4 h
% done: 50 %

3) Some delay:
Estimated Time: 8 h
Spent Time: 8 h
Remaining Time: 4 h
% done: 50 %
And since Spent Time + Remaining Time > Estimated Time, we have a delay, and then we should get the red bar to signal it. :D

#5 Updated by Terence Mill about 7 years ago

+1 for a new optional fieled with configurable algorithms from selection below

#6 Updated by Thanasis Karapatis about 6 years ago

+1

#8 Updated by Go MAEDA almost 2 years ago

  • Subject changed from Calculate the issue done ratio to Calculate the issue done ratio from estimated and spent time

#9 Updated by Go MAEDA almost 2 years ago

  • Category set to Issues

Also available in: Atom PDF