You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The lock/unlock feature needs to properly handle the disabled state of all fields. When in the locked state, all relevant fields should be disabled, preventing users from editing or interacting with them. This ensures a consistent and controlled user experience.
Screenshare.-.2025-02-26.5_31_05.PM.1.mp4
Proposed Objective
Core Features
Proposed Priority
Priority 3 - Average
Acceptance Criteria
When the feature is locked, all editable fields should be disabled.
Users should not be able to modify or interact with any locked fields.
When unlocked, fields should return to their editable state as expected.
The UI should visually indicate the disabled state when fields are locked.
Ensure proper handling of disabled fields across different input types (text, dropdowns, checkboxes, etc.).
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
The text was updated successfully, but these errors were encountered:
Parent Issue
No response
Task
The lock/unlock feature needs to properly handle the disabled state of all fields. When in the locked state, all relevant fields should be disabled, preventing users from editing or interacting with them. This ensures a consistent and controlled user experience.
Screenshare.-.2025-02-26.5_31_05.PM.1.mp4
Proposed Objective
Core Features
Proposed Priority
Priority 3 - Average
Acceptance Criteria
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
The text was updated successfully, but these errors were encountered: