Open arcady-zherdev opened 3 weeks ago
A workaround to fix the issue is:
Ext.define('MyApp.Task', {
extend : 'Gnt.model.Task',
requires : ['Ext.Array'],
processLateStartDateValue : function (value, context) {
var project = this.getProject(),
options = context.options,
store = options.taskStore || this.getTaskStore(true),
projectEndDate = project ? project.getEndDate() : store.getProjectEndDate(),
// ..subtract duration
projectEndDateMinusDuration = this.endDateToStartDate(projectEndDate);
if (value > projectEndDateMinusDuration) {
value = projectEndDateMinusDuration;
}
return this.callParent([value, context]);
},
processLateEndDateValue : function (value, context) {
var project = this.getProject(),
options = context.options,
store = options.taskStore || this.getTaskStore(true),
projectEndDate = project ? project.getEndDate() : store.getProjectEndDate();
if (value > projectEndDate) {
value = projectEndDate;
}
return this.callParent([value, context]);
}
});
Reported here: https://forum.bryntum.com/viewtopic.php?t=29361
Incorrect late dates calculated for task 17 in the following dataset. The reason is a negative lag applied for its successor.