Nested events escape from their parent after drag&drop when parent is manuallyScheduled

[marciogurka]

Forum post

"Hello,

When rescheduling parent events around non-working time intervals, nested events may escape from their parent. The video below shows how it can happen after a couple drag&drops"

dragdropparent.mp4

nested-events.zip

[marciogurka]

The user added a new test scenario that could be related to this one, if not related, could be a new ticket.

When I drag a parent event over a downtime, you can see that if only the last child event is over the downtime, it will behave correctly, extending its time to account for the time lost during the non-working time. But all the other events that are not the last child will just start messing the entire structure instead of properly extending the time.

bryntum-child-events-issue-with-downtime.mp4

[marciogurka]

The new scenario will be fixed here #6821