Task #16625: File Reference: Users should only be allowed to enter Seal number and Seal type one at a time - FFA - Redmine

Actions

Copy link

Task #16625

closed

Task #18123: Ocean Sprint Planning for 04/06/2025 - 13/06/2025

File Reference: Users should only be allowed to enter Seal number and Seal type one at a time

Added by Redmine Admin 7 months ago. Updated 40 minutes ago.

Status:

Closed

Priority:

Normal

Assignee:

Start date:

04/17/2025

Due date:

06/13/2025

% Done:

100%

Estimated time:

3:00 h

Spent time:

4:30 h

GitLab ID:

2404

GitLab Milestone:

GitLab Ticket Number:

739

GitLab Time Logged:

16200

Lock Timeline Date:

gitlab project trace:

Ocean Sprint Planning for 04/06/2025 - 13/06/2025

Description

Acceptance criteria

The FFS system should accepts only a single Seal number and one seal type per input.
Seal numbers should be unique across all entries
After each Seal number and seal type is entered, the input field resets to allow the next entry
The "Add Seal Info" button is enabled once a valid Seal number and seal type are entered and Save or a seal number has been deleted
If duplicate Seal number is inserted twice error message appears "Seal number already in use"
Seal number textbox should accept alphanumeric characters and does not allow blank spaces

Refer to Maintenance screen, Add Client screen

GitLab Sync Log

[{"id": "24755", "author": "Vishesh Jodhoa", "hours": 3.0, "created": "2025-06-12T05:29:26.402Z", "log_date": "2025-06-10", "comment": "Imported from GitLab by @Vishesh Jodhoa on 2025-06-12T05:29:26.402Z: 3h-(3.0)h spend at: 2025-06-10", "status": "active", "deleted_by": "", "redmine_entry_id": 9574}, {"id": "26240", "author": "Yashvee Seetul", "hours": 1.5, "created": "2025-07-03T06:38:24.966Z", "log_date": "2025-07-02", "comment": "Imported from GitLab by @Yashvee Seetul on 2025-07-03T06:38:24.966Z: 1h 30m-(1.5)h spend at: 2025-07-02", "status": "active", "deleted_by": "", "redmine_entry_id": 9845}]