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 Binary, File, and Image fields should correctly handle the disabled state when the lock feature is activated. Users should not be able to upload, drag and drop, select existing files, or create new files when the system is locked. This ensures that no unauthorized changes can be made while in a locked state.
Proposed Objective
Code Maintenance
Proposed Priority
Priority 3 - Average
Acceptance Criteria
The Binary, File, and Image fields should be completely disabled when in the locked state.
Users should not be able to drag and drop files, choose a file, import from a URL, or create/select existing files.
The UI should visually indicate that the fields are disabled.
When unlocked, the fields should return to their normal interactive state.
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 Binary, File, and Image fields should correctly handle the disabled state when the lock feature is activated. Users should not be able to upload, drag and drop, select existing files, or create new files when the system is locked. This ensures that no unauthorized changes can be made while in a locked state.
Proposed Objective
Code Maintenance
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: