Project

General

Profile

Actions

Task #18438

closed

Task #18453: Ocean Sprint Planning for 01/07/2025 - 11/07/2025

File Reference - Container still displayed after already being used

Added by Redmine Admin 6 months ago. Updated about 3 hours ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Start date:
06/26/2025
Due date:
07/11/2025
% Done:

100%

Estimated time:
8:00 h
Spent time:
GitLab ID:
2895
GitLab Milestone:
GitLab Ticket Number:
713
GitLab Time Logged:
28800
Lock Timeline Date:
No
gitlab project trace:
Ocean Sprint Planning for 01/07/2025 - 11/07/2025

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}]

Actions #1

Updated by Redmine Admin 6 months ago

  • GitLab Sync Log updated (diff)
Actions #2

Updated by Redmine Admin 5 months ago

  • Parent task set to #18453
  • gitlab project trace set to Ocean Sprint Planning for 01/07/2025 - 11/07/2025
Actions #3

Updated by Redmine Admin 5 months ago

  • Due date changed from 06/26/2025 to 07/11/2025
  • Estimated time changed from 0:00 h to 8:00 h
Actions #4

Updated by Redmine Admin 5 months ago

  • Status changed from New to Development Done
  • % Done changed from 0 to 100
  • GitLab Time Logged changed from 0 to 28800
Actions #5

Updated by Redmine Admin 5 months ago

  • GitLab Sync Log updated (diff)
Actions #6

Updated by Redmine Admin 5 months ago

  • Status changed from Development Done to QA
Actions #7

Updated by Redmine Admin 13 days ago

  • Status changed from QA to Closed
Actions

Also available in: Atom PDF