Project

General

Custom queries

Profile

Actions
Copy link

Defect #4682

closed

Completed version with wrong progress bar status

Added by Christiaan Kras about 15 years ago. Updated 11 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Marius BĂLTEANU
Category:
Roadmap
Target version:
6.0.0
Start date:
2010-01-28
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed
Affected version:
1.1.2

Description

I have a version inside a project which only contains 2 bugs/issues. Both of them were fixed and percentage of completement is both at 100%. Yet, as you can see in the screenshot, it shows 100% complete, but according to the progress bar 1 issue isn't closed yet. Which is actually.

I've tried setting the completement status to 90%, save, and set it back to a 100%. But no luck.

I've setup my Redmine instance to check the commit messages in my repository. When it says closes/fixes #<issue nr> it sets the status to resolved and at 100% ready/complete. This so far hasn't lead to any problems before.

Files

Download all files
roadmap-percentage-bug.PNG (15 KB) roadmap-percentage-bug.PNG Christiaan Kras, 2010-01-28 16:39
wrong_completed_percent_computation_with_0_time_issues.patch (4.07 KB) wrong_completed_percent_computation_with_0_time_issues.patch Etienne Massip, 2011-04-13 20:59
wrong_completed_percent_computation_with_0_time_issues.patch (4.4 KB) wrong_completed_percent_computation_with_0_time_issues.patch v2 Etienne Massip, 2011-04-16 18:04

Related issues

Related to Redmine - Feature #2182: Weighted version completion percentageClosed2008-11-13

Actions
Related to Redmine - Defect #24457: Progress of version should be calculated the same way as parent tasksClosedMarius BĂLTEANU

Actions
#3

Updated by Etienne Massip almost 14 years ago

  • Target version set to Candidate for next minor release
  • Affected version (unused) changed from 0.9.0 to 1.1.2
  • Affected version changed from 0.9.0 to 1.1.2
#4

Updated by Etienne Massip almost 14 years ago

#6

Updated by Etienne Massip almost 14 years ago

#8

Updated by Marius BĂLTEANU almost 6 years ago

  • Related to Defect #24457: Progress of version should be calculated the same way as parent tasks added
#9

Updated by Marius BĂLTEANU almost 6 years ago

  • Status changed from New to Confirmed
  • Target version changed from Candidate for next minor release to 4.1.0
#10

Updated by Go MAEDA over 5 years ago

  • Target version changed from 4.1.0 to 4.2.0
#11

Updated by Marius BĂLTEANU about 4 years ago

  • Target version changed from 4.2.0 to 5.0.0
#12

Updated by Marius BĂLTEANU about 3 years ago

  • Target version changed from 5.0.0 to 5.1.0
#13

Updated by Go MAEDA over 1 year ago

  • Target version changed from 5.1.0 to 6.0.0
#14

Updated by Marius BĂLTEANU 11 months ago

  • Status changed from Confirmed to Closed
  • Assignee set to Marius BĂLTEANU
  • Resolution set to Fixed
Actions
Copy link

Also available in: Atom PDF