Project

General

Profile

Actions

Task #18921

open

Task #19002: Sprint Planning for 03/11/2025 - 14/11/2025

File Reference - "Save as Draft" Functionality

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

Status:
QA
Priority:
Normal
Assignee:
-
Start date:
10/16/2025
Due date:
11/14/2025 (26 days late)
% Done:

40%

Estimated time:
40:00 h
Spent time:
GitLab ID:
3381
GitLab Milestone:
GitLab Ticket Number:
972
GitLab Time Logged:
57600
Lock Timeline Date:
No
gitlab project trace:
Sprint Planning for 03/11/2025 - 14/11/2025

Description

The system should allow the user to save a File Reference as a draft without requiring to fill all mandatory fields,
so that he can avoid losing entered data when validation errors or missing dependencies occur (e.g., missing shipment cost, client details, etc.), and continue editing later without data loss.

Currently, when users save a File Reference and an error occurs (e.g., missing linked data or required fields). As a result, users must exit the screen to complete the missing information in another module, causing them to lose all previously entered data and re-enter everything from scratch.

Acceptance Criteria

  • Save as Draft
    • The user can click a “Save as Draft” button at any time.
    • The system saves all entered data without validating mandatory fields.
    • The record is saved with a status “Draft” and can be reopened and completed later.
    • Draft records are clearly indicated in the File Reference list (e.g., status as “Draft”).
  • Save Final
    • The system performs full validation automatically when the user updates the HBL status to “Confirmed” or “Approved.”
    • If any required data is missing or invalid, the system should:
      • Prevent the status change to “Confirmed” or “Approved.”
      • Display specific validation messages identifying the missing or incorrect information.
      • Retain all entered data on the screen to allow the user to make corrections without data loss.
    • Once validation passes successfully, the HBL status is updated, and is marked as Confirmed/Approved.
    • If any required data is missing (e.g., client or shipment cost details), the system displays specific validation messages without clearing the form.

GitLab Sync Log

[{"id": "33235", "author": "Vishesh Jodhoa", "hours": 6.0, "created": "2025-10-31T11:33:36.796Z", "log_date": "2025-10-28", "comment": "Imported from GitLab by @Vishesh Jodhoa on 2025-10-31T11:33:36.796Z: 6h-(6.0)h spend at: 2025-10-28", "status": "active", "deleted_by": "", "redmine_entry_id": 11073}, {"id": "33234", "author": "Vishesh Jodhoa", "hours": 8.0, "created": "2025-10-31T11:32:32.405Z", "log_date": "2025-10-31", "comment": "Imported from GitLab by @Vishesh Jodhoa on 2025-10-31T11:32:32.405Z: 1d-(8.0)h spend at: 2025-10-31", "status": "active", "deleted_by": "", "redmine_entry_id": 11074}, {"id": "34192", "author": "Avisham", "hours": 2.0, "created": "2025-11-19T07:26:42.335Z", "log_date": "2025-11-18", "comment": "Imported from GitLab by @Avisham on 2025-11-19T07:26:42.335Z: 2h-(2.0)h spend at: 2025-11-18", "status": "active", "deleted_by": "", "redmine_entry_id": 11308}]

Actions

Also available in: Atom PDF