Project

General

Profile

Actions

Task #18435

open

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

FFS_Import/Export_Shipment Classification

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

Status:
QA
Priority:
Normal
Assignee:
-
Start date:
06/26/2025
Due date:
07/11/2025 (about 5 months late)
% Done:

12%

Estimated time:
120:00 h
Spent time:
GitLab ID:
2898
GitLab Milestone:
GitLab Ticket Number:
716
GitLab Time Logged:
54000
Lock Timeline Date:
No
gitlab project trace:
Ocean Sprint Planning for 01/07/2025 - 11/07/2025

Description

Purpose of this user story:

On a vessel / Vessel schedule, we can have one or multiple shipments.

Example:

MSC IBERIS - (Linked to a Master File Ref - Already Exists)

  • Shipment 1 - (Sub File - Presently shown as 122, 123)
  • Shipment 2

image.png{width=926 height=137}

Why we need this?

A File reference should be link to a shipment only not the overall vessel.

What problem we are facing right now?

All Cost and Sales / Volume are being merged together when having multiple shipments on a vessel.

How we are addressing the problem with this user story?

We should take into consideration an additional layer know as 'Shipment' (where the ref 122 represents a shipment).

The structure of Both Import / Export Consignment should read as per Below.

  1. Vessel - Linked with a Unique Master Reference (we already have).

    (a) Shipment - A vessel can contain one or multiple shipment and each shipment shall be covered by a Booking number / or Master BL number.

  2. Only one file reference shall be used per shipment.

  3. Cost and sales to be calculated 'Per shipment'.

For any Additional information, concerning the subject please reach out to me


GitLab Sync Log

[{"id": "26439", "author": "Avisham", "hours": 7.0, "created": "2025-07-07T12:10:30.853Z", "log_date": "2025-07-06", "comment": "Imported from GitLab by @Avisham on 2025-07-07T12:10:30.853Z: 7h-(7.0)h spend at: 2025-07-06", "status": "active", "deleted_by": "", "redmine_entry_id": 9880}, {"id": "26497", "author": "Avisham", "hours": 1.0, "created": "2025-07-09T05:49:59.065Z", "log_date": "2025-07-08", "comment": "Imported from GitLab by @Avisham on 2025-07-09T05:49:59.065Z: 1h-(1.0)h spend at: 2025-07-08", "status": "active", "deleted_by": "", "redmine_entry_id": 9903}, {"id": "26493", "author": "Avisham", "hours": 5.0, "created": "2025-07-09T05:10:06.456Z", "log_date": "2025-07-07", "comment": "Imported from GitLab by @Avisham on 2025-07-09T05:10:06.456Z: 5h-(5.0)h spend at: 2025-07-07", "status": "active", "deleted_by": "", "redmine_entry_id": 9904}, {"id": "26517", "author": "Avisham", "hours": 1.0, "created": "2025-07-10T05:17:37.691Z", "log_date": "2025-07-09", "comment": "Imported from GitLab by @Avisham on 2025-07-10T05:17:37.691Z: 1h-(1.0)h spend at: 2025-07-09", "status": "active", "deleted_by": "", "redmine_entry_id": 9909}, {"id": "26578", "author": "Avisham", "hours": 1.0, "created": "2025-07-11T07:54:14.187Z", "log_date": "2025-07-10", "comment": "Imported from GitLab by @Avisham on 2025-07-11T07:54:14.187Z: 1h-(1.0)h spend at: 2025-07-10", "status": "active", "deleted_by": "", "redmine_entry_id": 9919}]

Actions

Also available in: Atom PDF