Tasks loaded in in a calendars non-working time are set to 0 duration

[arobins]

Hi,

We have noticed that loading tasks without a duration but with the start and end date in non-working time into Gantt with loadInlineData causes the task to have a 0 duration and it does not shift the task to working time.

You can see this happening in this codepen: https://codepen.io/ajrobinscertinia/pen/zxovmRR

Task 1 shows the issue, and task 2 is a control. Task 1 is a 0 duration task in non-working time.

We expected the duration to be calculated based on the dates as is done with tasks normally but since it changes the dates to be the same the duration is lost.

Thank you

[alex.l]

Thank you for the report and clear description! Here is a ticket to track the status: https://github.com/bryntum/support/issues/13135
You can subscribe on ticket updates to be notified when it's done.

[arobins]

Hi,

I've noticed this has been marked as not a bug. Could we have a description as to why? Our customers are able to change task dates outside of Gantt, so they can be non-working time when they load in - then Gantt sets both dates to be the same, which loses the end dates on save.

[Arc]

Hello,

The ticket is closed because in the reported case the Gantt works as it's designed.

The task in your report has startDate and endDate provided and duration value is omitted which means it will be calculated as the amount of working time between the provided dates. The amount of working time between the provided dates it zero.

If you want the task to shift to the next working time slot you should either:
1) provide its duratiion value
2) provide data where working time configuration is aligned with task dates
3) or implement some custom logic of calculating dates and duration

Best regards,
Arcady