Project

General

Profile

Actions

Defect #8742

closed

% done in parent task is incorrect

Added by Wendy Wong over 12 years ago. Updated about 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Issues planning
Target version:
-
Start date:
2011-07-04
Due date:
% Done:

0%

Estimated time:
Resolution:
Cant reproduce
Affected version:

Description

Hi,
I've created a parent task with 3 sub-tasks. All the sub-tasks have been closed with 100% but the % done in parent task is showing only 67% which is supposed to be 100%.

How can i rectify this problem as it affects my overall roadmap performance? Thanks


Files

parent_task.JPG (118 KB) parent_task.JPG Wendy Wong, 2011-07-04 04:04
Actions #1

Updated by Etienne Massip over 12 years ago

Any plugins that could explain this ?

What is the estimated time of each subtask ?

Actions #2

Updated by Etienne Massip over 12 years ago

  • Category changed from Roadmap to Issues planning
Actions #3

Updated by Wendy Wong over 12 years ago

Etienne Massip wrote:

Any plugins that could explain this ?

What is the estimated time of each subtask ?

----------------------------------------------
~~ No plugins are being used

~~ No estimated time defined for each subtask, only due dates are defined

Actions #4

Updated by Etienne Massip over 12 years ago

What are the start and due dates of each task, please ?

Actions #5

Updated by Wendy Wong over 12 years ago

Etienne Massip wrote:

What are the start and due dates of each task, please ?

Parent task
-----------
13 Apr 2011 - 8 Jun 2011

Sub tasks
----------
1. 16 Apr 2011 - 6 May 2011
2. 15 Apr 2011 - 15 May 2011
3. 10 May 2011 - 8 June 2011

Actions #6

Updated by Wendy Wong over 12 years ago

Any updates?

Actions #7

Updated by Anonymous about 6 years ago

Wasn't able to reproduce.
With each completed child issue the parent issue's % done grew by 1/3, so it's been changing as expected: 33-66-100%.

Actions #8

Updated by Guillermo ML about 6 years ago

Alexander Oleynikov wrote:

Wasn't able to reproduce.

The issue is 6 years old, I suppose it was solved some time ago. It works flawlessly on our 3.4.4 version.

Actions #9

Updated by Anonymous over 5 years ago

So maybe it's time to close it.

Actions #10

Updated by Go MAEDA about 5 years ago

  • Status changed from New to Closed
  • Priority changed from High to Normal
  • Resolution set to Cant reproduce

I am closing this issue. Please open a new issue if you encounter the same problem again.

Actions

Also available in: Atom PDF