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 Host/Folder field should correctly handle the disabled state when the lock feature is activated. This means that users should not be able to edit or interact with the field when the system is locked, ensuring data integrity and a controlled user experience.
Proposed Objective
Core Features
Proposed Priority
Priority 3 - Average
Acceptance Criteria
The Host/Folder field should be disabled when the lock state is active.
Users should not be able to type, search, or select a different host or folder when locked.
When unlocked, the field should return to its normal interactive state.
The UI should visually indicate that the field is disabled.
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
#31494
Task
The Host/Folder field should correctly handle the disabled state when the lock feature is activated. This means that users should not be able to edit or interact with the field when the system is locked, ensuring data integrity and a controlled user experience.
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: