Project

General

Profile

Actions

Task #16819

closed

Task #16360: Sprint Planning for 20/01/2025 - 31/01/2025

File Reference: Vessel space booking validation and uniqueness

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

Status:
Closed
Priority:
Normal
Assignee:
-
Start date:
12/19/2024
Due date:
12/19/2024
% Done:

100%

Estimated time:
48:00 h
Spent time:
GitLab ID:
1674
GitLab Milestone:
GitLab Ticket Number:
544
GitLab Time Logged:
61200
Lock Timeline Date:
No
gitlab project trace:
Sprint Planning for 20/01/2025 - 31/01/2025

Description

Description

Screen: Freight purchase and File reference

  1. Capacity Constraint: The total volume of cargo booked should not exceed the available space on the vessel.
    2. Uniqueness: Vessel departure date and voyage number combination must be unique.

Acceptance Criteria:

Scenario 1: Single HBL Entry

  • The user has purchased 30 cubic meters of space on Vessel 'ATOL'. On File Reference when the user attempts to book 35 cubic meters of cargo.The system should not allow the user to insert more than 35 meter cube, also a message should display indicating that "The booked volume exceeds the available space"

Scenario 2: Multiple HBL Entries

  • The user has purchased 30 cubic meters of space on Vessel 'ATOL'.On File Reference when the user does two House Bill of Lading (HBL) entries:
    • 1st HBL: 18 cubic meters
    • 2nd HBL: 19 cubic meters
    • Total: 37 cubic meters

The system should not allow the user to insert more than 35 meter cube, Also a message should display indicating that "The booked volume exceeds the available space"

Additional Scenario: The user has purchased 30 cubic meter of space on a vessel. User A does a File Reference and uses 25 cubic meter. Another user doing another file reference on the same vessel will not be allowed to insert more than 5 meter cube. A message should be displayed ' Exceed maximum cubic meter'

Uniqueness Check

* When verifying the meter cube a uniqueness check should be performed on the on fields "departure date" and "voyage number".


GitLab Sync Log

[{"id": "14633", "author": "Ra-ees Peeroo", "hours": 2.0, "created": "2025-01-31T10:23:49.671Z", "log_date": "2025-01-31", "comment": "Imported from GitLab by @Ra-ees Peeroo on 2025-01-31T10:23:49.671Z: 2h-(2.0)h spend at: 2025-01-31", "status": "active", "deleted_by": "", "redmine_entry_id": 8315}, {"id": "14557", "author": "Ra-ees Peeroo", "hours": 2.0, "created": "2025-01-31T06:44:09.856Z", "log_date": "2025-01-31", "comment": "Imported from GitLab by @Ra-ees Peeroo on 2025-01-31T06:44:09.856Z: 2h-(2.0)h spend at: 2025-01-31", "status": "active", "deleted_by": "", "redmine_entry_id": 8316}, {"id": "14543", "author": "Ra-ees Peeroo", "hours": 8.0, "created": "2025-01-31T05:53:36.740Z", "log_date": "2025-01-27", "comment": "Imported from GitLab by @Ra-ees Peeroo on 2025-01-31T05:53:36.740Z: 1d-(8.0)h spend at: 2025-01-27", "status": "active", "deleted_by": "", "redmine_entry_id": 8317}, {"id": "14355", "author": "Ra-ees Peeroo", "hours": 5.0, "created": "2025-01-28T07:02:39.091Z", "log_date": "2025-01-26", "comment": "Imported from GitLab by @Ra-ees Peeroo on 2025-01-28T07:02:39.091Z: 5h-(5.0)h spend at: 2025-01-26", "status": "active", "deleted_by": "", "redmine_entry_id": 8318}]

Actions #1

Updated by Redmine Admin 7 months ago

  • GitLab Sync Log updated (diff)
Actions #2

Updated by Redmine Admin 2 months ago

  • Status changed from QA to Closed
  • % Done changed from 35 to 100
Actions

Also available in: Atom PDF