nextcloud / nextcloud/deck

Undelete for boards

Open
#3,534 3 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Is your feature request related to a problem? Please describe.
Sometimes user accidently deleate a board. This removes everything related with the board and a restore is possible, but not very easy because many database entries and (sometimes) files are affceted.
If a board is shared with outhers and they have the right to manage the board, it can be deleted by them.
Sometimes this happes unwanted, because the user just want to get a better overview and since there is no grouping or hiding of boards is possible, the user creates this overview by deleting the board for everyone. Sure it's a fail of the user, but it's very bad to fix this, after it has been deleted.

Describe the solution you'd like
A board should just marked for deletion and the delete job should not run 5 minutes after marked for deletion. Better would be to make this time span configurable, so that a manager or admin can undelete the board without restoring the DB.

Describe alternatives you've considered
Alternative would be, that a deleted board would be exported to a textfile (or json or whatever) on server and could be reimported by admin.

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 by tracing the board deletion flow and its five-minute delete job, including the database entries and files it affects. Define how the retention period is configured and how a manager or admin can undelete a board, then verify restoration works without direct database recovery.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
backend, database
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.