nextcloud / nextcloud/deck

Boards are silently deleted when their owner is removed — no warning, no transfer option

Open
#8,208 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement needs discussion
Dominant language
JavaScript
Stars
1.4k
Forks
354
Avg merge
1d 10h
Merged PRs (30d)
43

Description

Describe the bug

When a Nextcloud admin deletes a user, the admin UI offers to transfer that user's files to another account. However, Deck boards owned by the deleted user are silently deleted without warning and without any transfer option. The admin is never notified that boards will be lost.

Steps to reproduce

  1. Create one or more Deck boards as (or shared with) a user who owns them.
  2. As an admin, navigate to Settings → Users and delete that user.
  3. In the deletion dialog, choose to transfer files to another user and confirm.
  4. Observe: the files are transferred correctly, but all Deck boards owned by the deleted user are gone — no warning was shown, and no transfer option was offered for boards.

Expected behavior

Deck should integrate with Nextcloud's user-deletion hook (OCP\User\Events\BeforeUserDeletedEvent / file-transfer mechanism) so that at least one of the following happens:

  • Board ownership is transferred to the user selected in the "transfer files to" dialog, or
  • The admin is clearly warned that boards will be permanently deleted and must confirm this explicitly before the deletion proceeds.

Silently discarding boards during user deletion is a data-loss scenario. Users have no way to recover the content once the account is removed.

Additional context

  • Related: #1163 — admins can sometimes end up with orphaned boards they cannot manage; the root cause is the same missing integration with the user-deletion lifecycle.
  • Nextcloud's core already provides a clean hook for apps to participate in user deletion and the file-transfer flow; Deck should register a handler there.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at Deck's integration with Nextcloud's BeforeUserDeletedEvent and the existing file-transfer flow described in the issue. Reproduce deletion through Settings → Users, then trace the user-deletion path. Done means owned boards are transferred to the selected account or the admin receives and confirms an explicit board-loss warning.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.