Project

General

Profile

Actions

Task #18919

open

Task #18880: Sprint Planning for 20/10/2025 - 31/10/2025

Shipment Cost - not to be mandatory - should be configurable in settings

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

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

43%

Estimated time:
16:00 h
Spent time:
GitLab ID:
3383
GitLab Milestone:
GitLab Ticket Number:
974
GitLab Time Logged:
25200
Lock Timeline Date:
No
gitlab project trace:
Sprint Planning for 20/10/2025 - 31/10/2025

Description

By default, the system requires users to input shipment cost details before creating a File Reference. However, MCL and CPW have requested that the Shipment Cost section not be mandatory, as they will not record cost data in the system.
Not using this functionality, however, has a significant impact on the Cost and Sales section — users will not have access to profitability charts or reports derived from cost data. Therefore, a configurable solution is required so that the rule can be applied flexibly per client without affecting others.

Acceptance Criteria

  1. Configuration Setting
    • A new configuration option should be available under "Configuration Settings" (e.g., checkbox or toggle):
      Require Shipment Cost Entry: [Yes/No]
    • In the configuration screen, clearly label the toggle or checkbox with contextual help text:
      “When disabled, Shipment Cost will not be required for File References. Profitability reports and charts will be unavailable.”
    • When set to No, the system should not enforce the requirement to input Shipment Cost for that specific client.
    • When set to Yes, Shipment Cost remains mandatory before creating the File Reference.
  2. System Behaviour – When Shipment Cost Is Not Mandatory
    • Users can create and save/confirm/approve File References without entering Shipment Cost.
    • The Cost and Sales section remains accessible with only the volume chart but will also display a notice/warning:
      “Shipment Cost not recorded – Profitability reports and charts will not be available.”
    • All validations related to missing Shipment Cost should be bypassed for that client.
  3. System Behaviour – When Shipment Cost Is Mandatory
    • The system must continue to enforce existing validation rules before allowing the File Reference to reach Confirmed or Approved status.
  4. Impact on Reports and Charts
    • For clients with Shipment Cost disabled:
      • Cost and Sales PDF will not be available.
    • For clients with the setting enabled, all reports and charts function normally.

GitLab Sync Log

[{"id": "32443", "author": "Avisham", "hours": 3.0, "created": "2025-10-22T10:40:31.772Z", "log_date": "2025-10-22", "comment": "Imported from GitLab by @Avisham on 2025-10-22T10:40:31.772Z: 3h-(3.0)h spend at: 2025-10-22", "status": "active", "deleted_by": "", "redmine_entry_id": 10941}, {"id": "32541", "author": "Avisham", "hours": 4.0, "created": "2025-10-23T11:42:53.285Z", "log_date": "2025-10-22", "comment": "Imported from GitLab by @Avisham on 2025-10-23T11:42:53.285Z: 4h-(4.0)h spend at: 2025-10-22", "status": "active", "deleted_by": "", "redmine_entry_id": 10964}]

Actions #1

Updated by Redmine Admin about 2 months ago

  • GitLab Sync Log updated (diff)
Actions #2

Updated by Redmine Admin about 2 months ago

  • Due date changed from 10/16/2025 to 10/31/2025
  • Status changed from New to Development Done
  • GitLab Time Logged changed from 0 to 10800
Actions #3

Updated by Redmine Admin about 2 months ago

  • GitLab Sync Log updated (diff)
Actions #4

Updated by Redmine Admin about 2 months ago

  • Status changed from Development Done to QA
  • % Done changed from 0 to 43
  • Estimated time changed from 0:00 h to 16:00 h
  • GitLab Time Logged changed from 10800 to 25200
Actions #5

Updated by Redmine Admin about 2 months ago

  • GitLab Sync Log updated (diff)
Actions

Also available in: Atom PDF