Project

General

Profile

Actions

Feature #7545

open

Calculate the issue done ratio from estimated and spent time

Added by Luis Serrano Aranda almost 13 years ago. Updated over 5 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Issues
Target version:
-
Start date:
2011-02-04
Due date:
% Done:

0%

Estimated time:
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 configurationNew

Actions
Related to Redmine - Feature #11999: Calculating issue done ratio based on "Estimated Time" and "Spent Time" - selectable by project (not globally)New

Actions
Actions #1

Updated by Adam Piotr ┼╗ochowski almost 13 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

Actions #2

Updated by LEXO IT Services Switzerland about 11 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".

Actions #3

Updated by Samuel GABILLARD about 11 years ago

+1

Actions #4

Updated by Gorka Siverio almost 11 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

Actions #5

Updated by Terence Mill almost 11 years ago

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

Actions #6

Updated by Thanasis Karapatis almost 10 years ago

+1

Actions #7

Updated by Luis Serrano Aranda almost 10 years ago

+1

Actions #8

Updated by Go MAEDA over 5 years ago

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

Updated by Go MAEDA over 5 years ago

  • Category set to Issues
Actions

Also available in: Atom PDF