プロジェクト

全般

プロフィール

Vote #66447

未完了

Completed version with wrong progress bar status

Admin Redmine さんが約2年前に追加. 約2年前に更新.

ステータス:
Confirmed
優先度:
通常
担当者:
-
カテゴリ:
Roadmap_22
対象バージョン:
開始日:
2010/01/28
期日:
進捗率:

0%

予定工数:
category_id:
22
version_id:
176
issue_org_id:
4682
author_id:
11189
assigned_to_id:
0
comments:
12
status_id:
9
tracker_id:
1
plus1:
0
affected_version:
closed_on:
affected_version_id:
31
ステータス-->[Confirmed]

説明

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 # it sets the status to resolved and at 100% ready/complete. This so far hasn't lead to any problems before.


journals

Some extra info.

The last issue I changed from resolved to closed also had an time estamate which I changed to 0 whilst closing the issue. Maybe something went wrong here?
--------------------------------------------------------------------------------
If a issue has the expected time set to 0.0 the earlier reported error happens. After removing it and saving the issue the problem is solved.

Seems to me that the part that calculates the progress should ignore issues with a expected time of 0.
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Here's a patch.

I believe there is a similar issue with done percent computation for a task with subtasks.
--------------------------------------------------------------------------------
There is a very simpler patch which consists to add in @Version#closed_pourcent@ the test
<pre><code class="ruby">
...
if open_issues_count == 0
100
...</code>
</pre>
which already exists in @Version#completed_pourcent@.

--------------------------------------------------------------------------------
Full patch with tests.

Basically there are two possible calculation (depending on whether there is a total time estimated), which was intended to be prevented in #2182.

--------------------------------------------------------------------------------
This issue still can be reproduced in Redmine 3.2.0.
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
I'm assigning this to version:"4.1.0" to be fixed together with #24457.
--------------------------------------------------------------------------------


related_issues

relates,Closed,2182,Weighted version completion percentage
relates,New,24457,Progress of version should be calculated the same way as parent tasks

Admin Redmine さんが約2年前に更新

  • カテゴリRoadmap_22 にセット
  • 対象バージョン5.1.0_176 にセット

他の形式にエクスポート: Atom PDF

いいね!0
いいね!0