Project

General

Profile

Actions

Task #19548

closed

MCL/CPW - Add "Delete" Button in Charge Template Retrieve Screen

Added by Redmine Admin 5 months ago. Updated 3 months ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Start date:
03/17/2026
Due date:
03/17/2026
% Done:

100%

Estimated time:
6:00 h
Spent time:
GitLab ID:
4020
GitLab Milestone:
GitLab Ticket Number:
1288
GitLab Time Logged:
14400
Lock Timeline Date:
No
gitlab project trace:

Description

MCL/CPW has requested the ability to delete charge templates directly from the Charge Template Retrieve (List) screen in the Maintenance module.

Currently, the system provides a Deactivate option, which should remain unchanged. However, the client requires an additional Delete option to permanently remove charge templates when needed.

Current Behavior

  • Users can:
    • View charge templates
    • Edit charge templates
    • Deactivate charge templates
  • Users cannot permanently delete a charge template from the list screen

Expected Behavior

  • Add a "Delete" button/icon in the Actions column for each charge template row
  • This should be an additional action, not replacing Deactivate
  • Clicking the delete button should:
    1. Prompt a confirmation dialog (e.g., "Are you sure you want to permanently delete this charge template?")
    2. On confirmation, permanently delete the selected charge template
    3. Refresh the list to reflect the removal
    4. Display a success or error notification

Functional Requirements

  • Deletion should:
    • Permanently remove the record (based on system’s deletion rules)
  • Error handling:
    • Display clear error messages if deletion fails
  • Permissions:
    • Restrict delete action based on user roles—should be as an authority

Acceptance Criteria

  • Delete button is available in the Actions column
  • Deactivate functionality remains unchanged and usable
  • Confirmation dialog appears before deletion
  • Confirmation message clearly states permanent deletion
  • Charge template is removed after confirmation
  • List refreshes automatically after deletion
  • Success message is displayed
  • Error handling is implemented
  • Permission checks are enforced

Notes

  • Client requirement: Both Deactivate and Delete should coexist
  • Deactivate will continue to be used for temporary disabling
  • Delete will be used for permanent removal

GitLab Sync Log

[{"id": "40540", "author": "Avisham", "hours": 2.0, "created": "2026-03-18T10:05:30.408Z", "log_date": "2026-03-17", "comment": "Imported from GitLab by @Avisham on 2026-03-18T10:05:30.408Z: 2h-(2.0)h spend at: 2026-03-17", "status": "active", "deleted_by": "", "redmine_entry_id": 12680}, {"id": "40593", "author": "Avisham", "hours": 2.0, "created": "2026-03-20T05:55:44.185Z", "log_date": "2026-03-19", "comment": "Imported from GitLab by @Avisham on 2026-03-20T05:55:44.185Z: 2h-(2.0)h spend at: 2026-03-19", "status": "active", "deleted_by": "", "redmine_entry_id": 12693}]

Actions

Also available in: Atom PDF