nickolay wrote:The duration of the task is increased only by the intervals, which are "working" in the task's own calendar and in the calendar of at least one assigned resource.
Oh, that last condition is critical. Now I get it. I think once the issues you're working on are fixed, I'll be able to build a working calendar structure.
start date of the task: Apr 02 2020 08:00:00
end date of the task: Apr 09 2020 17:00:00
duration of the task: 5d (40 hours)
- Task is using calendar 1, "inherited" from the project
- Moved the "holiday" in the calendar1 to April (previously was in May)
- resource 15 does not contribute any effort at all, because it is on the calendar that gives empty intersection with the task calendar
- 04/02 - 04/03 - 8 hours of effort, contributed by resource_18, 8 hours of duration
- 04/03 - 04/04 - 0 hours of effort, 0 hours of duration - "holiday" in the calendar1
- 04/04 - 04/06 - 0 hours of effort, 0 hours of duration - weekend
- 04/06 - 04/09 - 16 * 3 hours of effort, contributed by resource_18, resource_19, 8 * 3 hours of duration
- 04/09 - 04/10 - 16 hours of effort, contributed by resource_18, resource_19, 8 hours of duration
- in total, 8 + 16 * 3 + 16 = 72h effort, 8 + 8 * 3 + 8 = 40h duration
- Duration conversion uses calendar 1
- "unspecifiedTimeIsWorking": false for all child calendars (important)
Still have few tests to fix, which are unrelated to scheduling modes, then the integration tests. Hopefully will be merged early-mid next week and will be available in nightly builds.
Using 2020-05-06-next I get an error saying Bundle included twice. setVersion('gantt', '2.1.2'); is indeed called twice (duplicated line) so I just removed one of them and then it loads fine. Then using the data in your previous post, I get Error: Invalid start date.
Using 2020-05-06-release it starts ok but when I switch tabs in the task editor I always get the same fields so I can't get the Advanced tab fields. But I can fiddle with the effort field and check the behavior.
So for 72 hours effort, the scheduler says the task should end on april 9th at 17h00. Let's check that
April 2nd: Ernest is off, that leaves Eli for 8 hours (day) and Doris for 4 hours (evening) = 12 hours. 60 hours left to do.
April 3rd: Day shift is off. That leaves Doris for 4 hours (evening) = 4 hours. 56 hours left to do.
April 4th and 5th are week end
April 6th: Everyone works so Eli and Ernest 8 hours each (day), plus Doris for 4 hours (evening) = 20 hours. 36 hours left to do.
April 7th, Everyone works so Eli and Ernest 8 hours each (day), plus Doris for 4 hours (evening) = 20 hours. 16 hours left to do.
April 8th, Everyone works but for the 16 remaining hours, the day shift is sufficient: Eli and Ernest 8 hours each (day) = 16 hours. 0 hours to do at 17h00.
So the task should end on April 8th at 17h00.
If I reduce the effort, I can see the problem is in the first few days. Let's say 14 hours. The scheduler says the task should end on april 6th at 11h00. Hmm that's odd. Let's see:
April 2nd: Ernest is off, that leaves Eli for 8 hours (day) and Doris for 4 hours (evening) = 12 hours. 2 hours left to do.
April 3rd: Day shift is off. That leaves Doris for 4 hours (evening) but only 2 hours are left to do so task ends at 20h00.
So the task should end on April 3rd at 20h00.
Does that make sens?
EDIT
Oh I get it now.
resource 15 does not contribute any effort at all, because it is on the calendar that gives empty intersection with the task calendar
With that in mind, the results are ok. I'll have to think of another way to setup the calendar tree. I'll do some tests.
I noticed something though. The task is set to fixed units and effort driven. If I postpone the start date, the effort increases! I don't believe that's intended, is it?
I noticed something though. The task is set to fixed units and effort driven. If I postpone the start date, the effort increases! I don't believe that's intended, is it?