Project

General

Profile

Actions

Task #16770

closed

Task #16612: Ocean Sprint Planning for 06/05/2025 - 16/05/2025

1 Master File reference for multiple file references

Added by Redmine Admin 7 months ago. Updated about 1 hour ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Start date:
01/17/2025
Due date:
05/16/2025
% Done:

100%

Estimated time:
8:00 h
Spent time:
GitLab ID:
1781
GitLab Milestone:
GitLab Ticket Number:
593
GitLab Time Logged:
21600
Lock Timeline Date:
No
gitlab project trace:
Ocean Sprint Planning for 06/05/2025 - 16/05/2025

Description

File Reference screen chnages.

Acceptance Criteria:

1.     Remove Release Order from File Reference Screen

  1. The "Release Order" section is removed from the File Reference screen.

  2. Users will now manage container references and release orders only in the Freight Purchase screen.

    @edoo_noorjahan @surfooddeen_hashim As per sprint Planning, it has been decided to upload the release order in the file reference itself and it will automatically relate to any other file reference with same master file reference and same container no, once the container no is updated.

2.     Use Master File Reference in File References

  1. In a File Reference, when users select a Vessel Schedule, the system should retrieve the linked Master File Reference (e.g., EDL24MSFE0001) from Freight Purchase and display it in bold on Top of the File Reference screen.
  2. Note that the same Master File Reference will be used by different salespersons across multiple File References.
  3. Container textbox to be replaced by dropdown list

o   After selecting Vessel Schedule, when adding/editing a container, the Container ref textbox should be replaced by a dropdown list of all dummy/purchased containers.

  1. If ever there is no freight purchase for the vessel or user has not selected any vessel then user should be prompted to create Freight Purchase or at least create a Dummy Freight Purchase to be used in such cases.  Then after purchasing the freight, the user can then select the correct vessel and the corresponding container.

4.     Sync Container References Automatically

  1. The File Reference screen should retrieve the container reference from the linked Freight Purchase.
  2. If a user updates the Container Reference in Freight Purchase, the corresponding dummy reference in File Reference should automatically update.
  3. Relate to above discussion in sprint planning
  4. Add new column/parent grid in List of File References
    • Either add a parent grid for “Master File Reference” which when expanded display all Sub File References or add a new column “Master File Reference” in File Reference List.
    • Add a new textbox “Master File Reference” to allow the user to filter the list by “Master File Reference”.
    • @softwaredev team, create a separate ticket for this and link it with this ticket.

 


GitLab Sync Log

[{"id": "19755", "author": "Vishesh Jodhoa", "hours": 3.0, "created": "2025-03-31T09:32:48.849Z", "log_date": "2025-03-31", "comment": "Imported from GitLab by @Vishesh Jodhoa on 2025-03-31T09:32:48.849Z: 3h-(3.0)h spend at: 2025-03-31", "status": "active", "deleted_by": "", "redmine_entry_id": 8228}, {"id": "19723", "author": "Avisham", "hours": 3.0, "created": "2025-03-31T05:24:34.184Z", "log_date": "2025-03-27", "comment": "Imported from GitLab by @Avisham on 2025-03-31T05:24:34.184Z: 3h-(3.0)h spend at: 2025-03-27", "status": "active", "deleted_by": "", "redmine_entry_id": 8229}]

Actions

Also available in: Atom PDF