Actions
Task #19174
openTask #19157: Sprint Planning for 15/12/2025 - 26/12/2025
Vessel Schedule - Previously uploaded Notice of Arrival (NOA) document persists when creating a new Vessel Schedule
Status:
Development Done
Priority:
Normal
Assignee:
-
Start date:
12/05/2025
Due date:
12/05/2025 (5 days late)
% Done:
0%
Estimated time:
0:00 h
Spent time:
GitLab ID:
3589
GitLab Milestone:
GitLab Ticket Number:
1060
GitLab Time Logged:
3600
Lock Timeline Date:
No
gitlab project trace:
Sprint Planning for 15/12/2025 - 26/12/2025
Description
Issue:
When creating a new Vessel Schedule after saving a previous one, the system incorrectly retains the previously uploaded Notice of Arrival (NOA) document. The NOA field should be cleared and reset to blank whenever the user starts creating a new Vessel Schedule.
Environment: Staging
Tenant: Maccs
Steps:
- Go to Vessel Schedule module.
- Click Create New Vessel Schedule.
- Choose vessel type (Import/Export or Import only).
- Fill in all mandatory details.
- Upload a Notice of Arrival (NOA) document.
- Click Save.
- Now click Create New Vessel Schedule again.
- The NOA document uploaded in the previous Vessel Schedule is still displayed when creating a new Vessel Schedule.
-
{width=466 height=265}
GitLab Sync Log
[{"id": "35219", "author": "Avisham", "hours": 1.0, "created": "2025-12-09T10:32:06.336Z", "log_date": "2025-12-08", "comment": "Imported from GitLab by @Avisham on 2025-12-09T10:32:06.336Z: 1h-(1.0)h spend at: 2025-12-08", "status": "active", "deleted_by": "", "redmine_entry_id": 11620}]
Actions