I seem to remember reporting this in the past. This is in reference to the schedule importer.
During import, the importer is treating any duty that is on the next Z-day as a separate duty period. This visually breaks up the Trip View and potentially causes legality issues.
Example in the screenshot:
A deadhead from YYZ-ORD starts on Z-date 29NOV. The duty period is supposed to continue with a deadhead from ORD-SDF on Z-date 30NOV (a 2h29m turn between deadheads). These two flights should be during the same duty periods that started on the 29th. The importer is putting them into two different duty periods and it requires manually building a new leg on the first duty period and completely deleting the second duty period... And until we get drag and drop capabilities, this is tedious.
During import, the importer is treating any duty that is on the next Z-day as a separate duty period. This visually breaks up the Trip View and potentially causes legality issues.
Example in the screenshot:
A deadhead from YYZ-ORD starts on Z-date 29NOV. The duty period is supposed to continue with a deadhead from ORD-SDF on Z-date 30NOV (a 2h29m turn between deadheads). These two flights should be during the same duty periods that started on the 29th. The importer is putting them into two different duty periods and it requires manually building a new leg on the first duty period and completely deleting the second duty period... And until we get drag and drop capabilities, this is tedious.
