nextcloud / nextcloud/deck

Option to Keep Assigned Users on Archived Cards

Open
#7,079 4 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

needs discussion
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.
When I archive a card in Deck, all assigned users are removed from the card. This is unexpected for my workflow, because I would like to keep track of who was responsible for a card, even after it is archived. Currently, there doesn’t seem to be a setting to control this behavior.

Describe the solution you'd like
I would like an option (either default or configurable) that allows assigned users to remain visible on cards after they are archived. This would help with accountability and tracking, especially when reviewing completed or archived tasks later.

Describe alternatives you've considered
I have checked the settings and documentation, but could not find a way to keep user assignments on archived cards. Manually noting assigned users before archiving is not practical.

Additional context
Tested on Deck version 1.15.1. The issue occurs for all users/cards, and is consistent across boards.
If this is intentional, please consider making it configurable, or clarify the reasoning in the documentation.

Thank you for considering this feature!

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

No files or tests are named. Start by tracing how Deck 1.15.1 archives cards and clears assignments, then determine whether retention should be default or configurable. Done means archived cards preserve visible assignees and the chosen behavior is covered by tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
full-stack
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.