[ANSWERED] nonWorkingTime feature stops working with large resources and assignments stores

[Jerther]

Hi!

We have noticed that the nonWorkingTime feature stops working when there are more than a certain combination of assignments and resources. I've managed to generate a (quite large) dataset to replicate the problem.

The scheduling engine seems to work fine though.

Here's the data on pastebin

And here's the Gantt config:

const project = new ProjectModel({
    transport : {
        load : {
            url : 'data_test.json'
        }
    }
});

new Gantt({
    adopt : document.body,

project : project,

columns : [
    { type : 'name', field : 'name', width : 250 }
],

features: {
    nonWorkingTime: true,

...

If you run this, the non working times won't be highlighted. If you remove either a resource or an assignment from either store in the source data, the nonworking times will be highlighted, as expected.

Using Gantt v2.1.3

[pmiklashevich]

Here's the data on pastebin

This service is not available at the moment. Could you please attach a zip file with data in Json we can replace "Gantt/examples/_datasets/launch-saas.json" file with?

[Jerther]

Wow that doesn't happen often

Here's the data!

[alex.l]

Hi Jerther,

Thanks for the report, I was able to reproduce the problem, the ticket has been created https://github.com/bryntum/support/issues/827

All best,
Alex