PercentDone loaded not correctly

[arcady]

I also don't know what happens. If you provide a runnable test case we'll take a look.

[miro]

Hi,

I will give you a scenario and want you clarify the formula regarding to children_duration.

Task Name			Start Date			End Date			Duration
Root Task			Jan-02-2023		Feb-12-2023			40 days
	Task 1			Jan-02-2023		Jan-10-2023			8 days
	Task 2			Jan-11-2023			Jan-11-2023			1 day
	Task 3			Jan-12-2023			Feb-12-2023			31 days
		Task 3.1		Jan-12-2023			Jan-15-2023			3 days
		Task 3.2		Feb-10-2023			Feb-12-2023			2 days

As the formula you sent me. I have:

• Children duration of Task 3 , it is 5 days (sum duration from Task 3.1 and Task 3.2)

I want to clarify children duration of Root Task. Is it 40 days (sum duration from Task 1, Task 2 and Task 3) or 14 days (sum duration from Task 1, Task 2 and children duration of Task 3)?

[arcady]

Root Task (and any other auto-scheduled summary task's) duration will be calculated as working time between its start and end dates. And a summary task start and end dates are calculated as min(child start date) and max(child end date) respectively.
This rolling up goes from the depth up to the root level.

[miro]

Can you please provide an answer to the example provided above? Let me copy and paste again to make it easy.

Task Name Start Date End Date Duration
Root Task Jan-02-2023 Feb-12-2023 40 days
Task 1 Jan-02-2023 Jan-10-2023 8 days
Task 2 Jan-11-2023 Jan-11-2023 1 day
Task 3 Jan-12-2023 Feb-12-2023 31 days
Task 3.1 Jan-12-2023 Jan-15-2023 3 days
Task 3.2 Feb-10-2023 Feb-12-2023 2 days

As the formula you sent me. I have:

Children duration of Task 3 , it is 5 days (sum duration from Task 3.1 and Task 3.2)
I want to clarify children duration of Root Task. Is it 40 days (sum duration from Task 1, Task 2 and Task 3) or 14 days (sum duration from Task 1, Task 2 and children duration of Task 3)?

[arcady]

Ah sorry. I thought the definition of duration for summary task was enough. Anyway as I already wrote above a task duration is amount of working time between its start and end dates.
So given the dates Task 3 and Root Task durations will be 31 and 40 days respectively.

[miro]

Hi,

I create some tasks as example I sent you at previous post. bryntum used 5 days of Task 3 to calculate children_duration of Root Task.

To verify your answer I made debug on calculatePercentDoneSummaryData method and get result:

 - Task 1: duration = 230400000 milliseconds = 8 days
 - Task 2: duration =  28800000 milliseconds = 1 day
 - Task 3: duration = 144000000 milliseconds = 5 days (which is wrong it have to = 31 days as your answer above)

==> is there a bug in your calculation percent done?

here is my screen shot:

PercentDone_3.PNG (161.44 KiB) Viewed 83 times

[arcady]

Please provide a runnable test case so I could check and tell if that's a bug.

[miro]

All the details are above. You can create the three tasks as per the screenshot,

Then advise what the expected result for task 3 - parent.

Currently, the scheduler is showing the Parent of Task 3 (3.1 & 3.2) = 5 days, which is wrong.
Because between tasks 3.1 & 3.2, there is a lag, and the duration is 31 days, not 5 days.
Hence, there is a bug, or the formula you provided is wrong.

[arcady]

I'm sorry but providing a test case is mandatory: viewtopic.php?f=1&t=772

Screenshots are nice but they do not provide all the data that could make a difference. Plus narrowing down set of task fields to start/end/duration also does give full picture. There are other fields/data affecting task scheduling (schedulingMode/effort/constraints/assignments/dependencies etc.).