nextcloud / nextcloud/deck

Deleting a list without deleting its archived daughter cards / Archiving a list with nothing but archived cards

Open
#7,490 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.

I archived a lot of cards, because I want to keep track of those cards even though they are marked as done. Up to the point where some lists became empty. So I deleted the list, forgetting that some archived cards actually belong to them. And it deleted those cards.

Describe the solution you'd like

I'd like a way to archive lists, keeping the hierarchy (ie the link with the cards that belonged to them in the past)

Describe alternatives you've considered

  • a list trashbin, or a card trashbin
  • at least a warning stating "All the cards in this list, including archived ones, will be deleted, do you want to delete anyway
  • or any combination of the above ("do you want to archive the list instead?", "Do you want to delete the list and keep the archived cards?", ...)

Additional context
Add any other context or screenshots about the feature request here.

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

The issue names no files, tests, or entry points. Start by locating list deletion and archived-card handling in the Deck code, then determine the intended behavior for lists containing archived cards. Done means the selected archive, warning, or retention behavior is implemented and verified for that case.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.