Defect #22504
closed
Progress bar calculation in 3.2
0%
Description
Starting with 3.2 and still an issue in 3.2.1 the progress bar calculation is questionable.
!Bildschirmfoto 2016-04-14 um 19.49.08.png!
My setup:- progress calculation by ticket status
- status "closed" and "invalid" are both marked as "closed" and "% done" is set to "100%"
All 50 closed tickets are either in the state "closed" or "invalid". So why is there a difference between "closed" and "done" in the progress table?
In this certain case, I would expect the "closed/done" progress part to be at 50% in the darker green tone and then I would expect for example 30% "work in progress" in the lighter green color for all the tickets being work in progress. This was the behaviour before 3.2.
Files
Updated by Toshi MARUYAMA almost 8 years ago
- Status changed from New to Needs feedback
I cannot see any difference in vanilla Redmine Web UI between 3.1 and 3.2.
Do you use plugin or theme and do these follow r14851 etc. change?
Updated by Tobias Fischer almost 8 years ago
This is the behaviour with default theme.
Unfortunately I cannot downgrade to 3.1 anymore, but as this issue arouse when I upgraded from 3.1 to 3.2 I'm pretty sure this hadn't been an issue before.
I hope you can agree with my conclusion, that the calculation seems to be wrong, right?
Updated by Jean-Philippe Lang almost 8 years ago
You must have some estimated times entered on some issues assigned to this version. It's taken into account to calculate the version progress. Can you list the 102 issues and check if there are some estimated times?
Updated by Tobias Fischer almost 8 years ago
toshio harita: Maybe... Since I got hundred's of tickets and this was an issue in our production environment, I'm not sure whether I can reproduce this or relate it to #23151
Anyways, this is my setup for issue done calculation:- Calculate the issue done ratio with:
use the issue status - Parent tasks attributes: % Done:
Calculated from subtasks
Since my setting for issue done ratio is based on the issue status field(!) I expect the estimated time not being taken into account when calculating the issue done ratio. Am I right?
Updated by Toshi MARUYAMA almost 8 years ago
Tobias Fischer wrote:
I expect the estimated time not being taken into account when calculating the issue done ratio. Am I right?
See #2182.
Updated by Jean-Philippe Lang almost 8 years ago
- Status changed from Needs feedback to Closed
Tobias Fischer wrote:
Since my setting for issue done ratio is based on the issue status field(!) I expect the estimated time not being taken into account when calculating the issue done ratio. Am I right?
The issue done ratio is based on the status, but the progress of the version is based on issues progress and estimated time. If you have one issue at 100% estimated to 5h and and one issue at 0% estimated to 10h, the global progress will be 33%, not 50%.
I'm closing it since it is the expected behaviour, as noted by Toshi in #2182.
Updated by Tobias Fischer almost 8 years ago
Oh, okay, sorry, didn't knew that and probably never experienced it before so I thought it was introduced with 3.2
Sorry for the trouble