Task #18438
closedTask #18453: Ocean Sprint Planning for 01/07/2025 - 11/07/2025
File Reference - Container still displayed after already being used
Description
Dear Avisham,
Refer to our conversation, please find below the test scenario which has been tested on staging.
Test Case:
1 MBL - MBL2606001
2 Cont - MAEU2606001 and FFFF2606002
and
1 MBL - MBL2606002
1 Cont - FFFF2606001
Please note that the shipment cost and the file reference (FCL) has been successfully validated.
- Shipment cost - Master file reference: EDL25MSFE06016
- File reference - EDL25SFI06011
After successful creation of the file reference: EDL25SFI06011 a new shipment cost has been created for container FFFF2606001.
The shipement cost has been successfully created for 1 container - (EDL25MSFE06016).
However, when creating the file reference for MBL2606002, we found that the user still have the posibility to use the container found on MBL2606001 (MBL and container which has already been used).
Furthermore, the user can select the container which has already been used in previous file reference and can also saved the transaction.
Proposed solution:
Once an FCL container has been used on a file reference, the user should not be ale to select this particular container on another file reference.
GitLab Sync Log
[{"id": "26208", "author": "Ra-ees Peeroo", "hours": 8.0, "created": "2025-07-02T11:01:13.109Z", "log_date": "2025-07-02", "comment": "Imported from GitLab by @Ra-ees Peeroo on 2025-07-02T11:01:13.109Z: 1d-(8.0)h spend at: 2025-07-02", "status": "active", "deleted_by": "", "redmine_entry_id": 9837}]