Our state of the art Gantt chart


Post by awendt »

A Gantt user reported a bug that they couldn't edit the date of a task. We investigated, and found that the reason they couldn't change the date was because the task was the successor of a finish-to-start dependency, and the user was trying to move the start date of the successor task before the end date of the predecessor task.
This is obviously not a bug, but it was hard for the user to tell because they had a large dependency chain.
Is there a way we could show the users a message explaining why they can't change a task's dates in this case (and other similar cases)?


Post by arcady »

There is a schedulingConflict event on the project that signalizes that a conflict has happened. It's not super informative in that version of the Gantt I'm afraid since it doesn't provide any useful info on what caused to the conflict.
But you can show a message box saying that a conflict happened at least.

We have upgraded that event and made a new UI informing user of conflicts, cycles and calendar misconfigurations that allows to handle such cases.
But it will appear in the Gantt 5.0.0.


Post by awendt »

Thank you! That's good news.
What's the release date for Gantt 5.0.0?


Post by mats »

ETA Q4 this year if all goes as planned!


Post by awendt »

When does the schedulingConflict event trigger?

We aren't seeing schedulingConflict events when trying to drag a successor task before its predecessor task (where the dependency between the two is a finish-to-start).


Post by alex.l »

Not for such operations like drag-n-drop yet, but for more complex. As example try to do incorrect changes for contraintType/contraintDate.

It will be improved and documented at version 5.0

All the best,
Alex


Post by awendt »

In version 5.0, will the schedulingConflict event trigger for the dependency-date-changing issue that I've described?


Post by alex.l »

No, it won't be triggered as far as I see in the current state of development. We will think about the logic and decide.
Try to use https://bryntum.com/docs/gantt/#Gantt/feature/TaskDrag#event-afterTaskDrop for now.
It has valid parameter, so you could show a notification that drag-n-drop is invalid, at least.

All the best,
Alex


Post by arcady »

Ah sorry I misread your scenario. Indeed that's not a scheduling conflict. If I understand correctly you drag a successor backwards and its predecessor pushes it and does not allow doing that.
Indeed no conflicts happen in that case.
All automatically scheduled tasks are placed at calculated start/end dates. Which is their ASAP (earliest possible) dates by default (could be also ALAP for a backward scheduled project).
So the successor dates are just calculated based on its constraints and dependencies which means according to the predecessor position.


Post Reply