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 Edit: Add the ability to lock and unlock content #30900

Open
john-thomas-dotcms opened this issue Dec 10, 2024 · 2 comments
Open

Content Edit: Add the ability to lock and unlock content #30900

john-thomas-dotcms opened this issue Dec 10, 2024 · 2 comments

Comments

@john-thomas-dotcms
Copy link
Contributor

Parent Issue

No response

User Story

As a content editor, I must be able to lock and unlock content, so I can perform workflow actions which require the content to be locked (such as save).

The current content edit screen allows users to lock and unlock content in 2 different ways:

  • Via workflow actions that contain the 'Lock content' and 'Unlock content` subactions.
  • Via "default" lock and unlock actions, which show as buttons above all other workflow action buttons, regardless of whether or not any lock/unlock workflow actions are available.

The new content edit screen already allows lock and unlock via Workflow actions. We need to give users the same ability to perform lock and unlock when no lock/unlock actions exist in the workflow.

To do this, we need to add a control to the content edit screen to allow the user to lock and unlock content.

Acceptance Criteria

  1. A lock/unlock control is visible in the content edit screen.
  2. The lock/unlock control is enabled when both of the following are true:
    • The current user has edit rights on the current contentlet.
    • The current user has access to any workflow action in the current workflow step which includes any save actionlet.
  3. The lock/unlock control is disabled when the current user does not have edit rights on the current contentlet.
  4. The lock/unlock control is disabled when the current user does not have access to any workflow action in the current step that includes a save actionlet.
  5. When the user locks or unlocks the content using the control, the change takes effect immediately.
    • The user does NOT need to execute a workflow action for the lock or unlock to take effect.
  6. When content is locked, the content edit window is closed, and the content is re-opened, it remains locked.
  7. When content is unlocked, the content edit window is closed, and the content is re-opened, it remains unlocked.
  8. If the content is not locked, and the user attempts to perform a workflow action from the content edit screen which performs a save or other actionlet that modifies the content:
    • If no other user has a lock on the contentlet, the action succeeds without error or notice.
    • If another user already has a lock on the contentlet, the user attempting the workflow action receives a popup with an error.

Proposed Objective

Core Features

Proposed Priority

Priority 1 - Show Stopper

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

@jdotcms
Copy link
Contributor

jdotcms commented Dec 10, 2024

Working on the BE part

@jdotcms jdotcms moved this from In Progress to Next 1-3 Sprints in dotCMS - Product Planning Dec 10, 2024
Copy link

@john-thomas-dotcms john-thomas-dotcms moved this from Next 1-3 Sprints to Current Sprint Backlog in dotCMS - Product Planning Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Current Sprint Backlog
Development

No branches or pull requests

2 participants