Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Content Lock/Unlock Management System #31288

Open
Tracked by #25445
oidacra opened this issue Jan 31, 2025 · 0 comments
Open
Tracked by #25445

Content Lock/Unlock Management System #31288

oidacra opened this issue Jan 31, 2025 · 0 comments

Comments

@oidacra
Copy link
Member

oidacra commented Jan 31, 2025

Parent Issue

#25445

User Story

As a content editor, I want to be able to lock/unlock content while editing, so I can prevent concurrent modifications and maintain data integrity, with clear visual indicators of the content's locked status and who has locked it.

Acceptance Criteria

UI Requirements:

  • Lock/unlock toggle switch must remain accessible when scrolling or switching tabs
  • Toggle switch must have clear visual enabled and disabled states
  • Control must remain visible at all times during content editing
  • Display informative hint/hover text when control is disabled
  • Show informational blue message bar when content is locked
  • Layout Page must inherit lock state from UVE (Universal Visual Editor)
  • All content must be in read-only state when locked
  • Switch should appear enabled even when user lacks unlock permissions
  • Send email notifications when content is unlocked by another user
  • Display notification message when returning to previously locked content

Message Display Requirements:

  • Show current lock status and owner
  • Display appropriate message based on user permissions
  • Show informative message about how to unlock content

Proposed Objective

Technical User Experience

Proposed Priority

Priority 2 - Important

Test Scenarios

Based on the user story provided:

  1. Lock Content Scenario:

    • Rose locks Blue Lake Post
    • System shows "Locked by Rose" message
    • All content becomes read-only
  2. Forgotten Lock Scenario:

    • Rose locks content, makes changes
    • Leaves content locked and goes on vacation
    • Marcie cannot edit content
    • Jayden (with permissions) unlocks content
    • Marcie can now edit content
  3. Permission Handling:

    • User without permission tries to unlock content
    • System shows "You don't have permissions" message
    • Toggle remains visible but cannot be activated

QA Notes & Workarounds

Test considerations:

  • Verify scroll behavior doesn't affect lock control visibility
  • Test tab switching maintains lock status
  • Verify read-only state of all form fields when locked
  • Test permission-based scenarios
  • Test all message variations
  • Verify lock status persistence after page refresh
  • Test accessibility of toggle switch and messages
  • Verify hover/hint text functionality
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Next 1-3 Sprints
Development

No branches or pull requests

1 participant