Actions
Task #16626
openTask #16323: Ocean Sprint Planning for 19/05/2025 - 30/05/2025
Clearing: Users should only be allowed to enter Seal number and Seal type one at a time
Status:
QA
Priority:
Normal
Assignee:
-
Start date:
04/17/2025
Due date:
04/17/2025 (about 8 months late)
% Done:
0%
Estimated time:
0:00 h
Spent time:
GitLab ID:
2403
GitLab Milestone:
GitLab Ticket Number:
738
GitLab Time Logged:
28800
Lock Timeline Date:
No
gitlab project trace:
Ocean Sprint Planning for 19/05/2025 - 30/05/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
{width=917 height=400}
GitLab Sync Log
[{"id": "22205", "author": "Gilles Mahomudally", "hours": 8.0, "created": "2025-04-28T05:22:18.975Z", "log_date": "2025-04-20", "comment": "Imported from GitLab by @Gilles Mahomudally on 2025-04-28T05:22:18.975Z: 1d-(8.0)h spend at: 2025-04-20", "status": "active", "deleted_by": "", "redmine_entry_id": 7995}]
Actions