Task #18918
openTask #18880: Sprint Planning for 20/10/2025 - 31/10/2025
File Reference - Same Port of Loading (PoL) and Port of Destination (PoD) should be entered several times
0%
Description
Currently, users are required to manually input the Port of Loading (PoL) at Import level, Port of Destination (PoD) ar Export level multiple times across different screens — namely Vessel Schedule, Master BL, Container Reference, and House BL.
This repetition increases data entry time, introduces inconsistency risks (e.g., mismatched ports between Master and House), and reduces operational efficiency.
Acceptance Criteria
-
Primary Source & Flow
- If PoL is captured at Vessel Schedule then in file reference, same PoL is auto-selected into Master BL, Container Ref, and House BL. Same applied for PoD
- If PoL is captured in file reference at Master level then same PoL is auto-selected into Container Ref, and House BL. Same applied for PoD
-
Override
- User may change the ports if needed.
-
Change in Vessel Schedule
- If PoL/PoD changes in Vessel Schedule then user gets a prompt:
“PoL/PoD changed. Update records in File Reference?” → Update All / Skip.
- If PoL/PoD changes in Vessel Schedule then user gets a prompt:
GitLab Sync Log
[{"id": "32936", "author": "Vishesh Jodhoa", "hours": 4.0, "created": "2025-10-27T05:08:47.974Z", "log_date": "2025-10-22", "comment": "Imported from GitLab by @Vishesh Jodhoa on 2025-10-27T05:08:47.974Z: 4h-(4.0)h spend at: 2025-10-22", "status": "active", "deleted_by": "", "redmine_entry_id": 10982}, {"id": "32937", "author": "Vishesh Jodhoa", "hours": 1.0, "created": "2025-10-27T07:39:07.594Z", "log_date": "2025-10-27", "comment": "Imported from GitLab by @Vishesh Jodhoa on 2025-10-27T07:39:07.594Z: 1h-(1.0)h spend at: 2025-10-27", "status": "active", "deleted_by": "", "redmine_entry_id": 10984}]