Daylight Saving Time(DST) problem (gantt4-beta2 && gantt 2.19

[misto]

1/ examples/datasets/launch-saas.json:

{
    "success" : true,

"project" : {
    "calendar"     : "general",
    "startDate"    : "2020-10-22"
},

  
"tasks" : {
    "rows" : [
        {
            "id": 1000,
            "name": "Launch SaaS Product",
            "percentDone": 50,
             "startDate": "2020-10-22",
             "endDate": "2020-11-04"
         }
      ]
  }
}

2/ open /examples/localization/

3/ Problems:
3.1 It shows endDate 03 Nov
3.2 If I try to change endDate to 10 nov it takes 25 oct (dst)
3.3 In edit mode duration is 12.958333333333334

[alex.l]

Hi misto,

I downloaded gantt4.0.0-beta-2 release from our Customer Zone and tried it with the JSON you attached. It shows me correct dates.
Unfortunately, I cannot reproduce all 3 your problems. Be aware that all parent tasks calculate depends on child tasks and if this is not full JSON, endDate may be re-calculated.

Actually, we need info about your timezone, and it will be very helpful if you'll attach the example you mentioned with your changes where you are able to reproduce this issue.

All best,
Alex

[misto]

Hi,

1/ Be aware that all parent tasks calculate depends on child tasks and if this is not full JSON, endDate may be re-calculated
In my example there are not parents.

2/ In 2.1.9 see: https://github.com/bryntum/support/issues/1432

3/ I re-downloaded gantt-beta-2 same result:

dst.png (125.28 KiB) Viewed 1207 times

[pmiklashevich]

Hello @misto

Please do not duplicate issues. The original thread is here: viewtopic.php?f=43&t=15112

You can subscribe to the git-hub issue to be notified when it's resolved & fixed. The status is "new" and we're planning to get it fixed as a patch release of 4.0. Please stay tuned!

Best,
Pavel

[misto]

Hello,
I reported same issue for gantt4 because there is not workaround.

This issue is very annoying for our customers (in 2.1.9). To set endDate 2020-10-27 they have to choose 2020-10-28.

[mats]

We'll do our best to fix this in an upcoming release!

[misto]

Thank you