Project

General

Profile

Actions

Task #18636

open

Task #18634: Sprint Planning for 25/08/2025 - 05/09/2025

Volume availability check not raising an alert when container reaches full capacity.

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

Status:
QA
Priority:
Normal
Assignee:
-
Start date:
09/01/2025
Due date:
09/05/2025 (about 3 months late)
% Done:

0%

Estimated time:
0:00 h
Spent time:
GitLab ID:
3160
GitLab Milestone:
GitLab Ticket Number:
877
GitLab Time Logged:
10800
Lock Timeline Date:
No
gitlab project trace:
Sprint Planning for 25/08/2025 - 05/09/2025

Description

The system allows adding HBLs exceeding container capacity under a single container reference in LCL shipments.

When working with LCL shipments, users can add multiple HBLs under a single container reference (e.g., 20FT with 30 m³ capacity). The system currently does not validate the container’s maximum volume. As a result, it is possible to add HBLs whose combined total volume exceeds the container’s actual capacity (e.g., 78 m³ under a 30 m³ container).

Environment: Staging V1.1.7

Steps to Reproduce

  1. Go to Shipment Cost → Create an Import shipment with multiple 20FT containers (30 m³ each).

    Screenshot 2025-09-01 143022.png{width="749" height="283"}

  2. Go to File Reference (MACCS25SFI09154), Add a container

    Screenshot 2025-09-01 143103.png{width="252" height="316"}

  3. Then add multiple HBLs under this container whose total volume exceeds 30 m³.

    • Example: 7 HBLs with a total volume = 78 m³ against a container capacity of 30 m³.

      image.png{width="889" height="189"}

The system should alert the user on creation and saving of HBLs once container capacity (30 m³) is reached. Flag an error or warning.

The system should validate total HBL volume against container capacity.

The user should receive an error/warning when attempting to exceed container volume.

The container reference cannot be saved if over-allocation occurs.

Note that same should be applied to Export Shipment - LCL also.


GitLab Sync Log

[{"id": "30085", "author": "Avisham", "hours": 3.0, "created": "2025-09-03T07:09:46.117Z", "log_date": "2025-09-02", "comment": "Imported from GitLab by @Avisham on 2025-09-03T07:09:46.117Z: 3h-(3.0)h spend at: 2025-09-02", "status": "active", "deleted_by": "", "redmine_entry_id": 10248}]

Actions #1

Updated by Redmine Admin 3 months ago

  • GitLab Sync Log updated (diff)
Actions #2

Updated by Redmine Admin 3 months ago

  • Due date changed from 09/01/2025 to 09/05/2025
  • Status changed from New to Development Done
  • Parent task set to #18634
  • GitLab Time Logged changed from 0 to 10800
  • gitlab project trace set to Sprint Planning for 25/08/2025 - 05/09/2025
Actions #3

Updated by Redmine Admin 3 months ago

  • GitLab Sync Log updated (diff)
Actions #4

Updated by Redmine Admin 3 months ago

  • Status changed from Development Done to QA
Actions

Also available in: Atom PDF