nextcloud / nextcloud/deck

Archived card listing

Open
#1,721 4 comments 15 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

The current way of listing archived cards is not optimal as we just show the archived cards in the same way as regular cards, grouped by their stack. In a kanban-like organization process cards most likely end up on a "Done" list or something similar where they are then archived from later on.

This results in the archived view being a long list of cards in the Done stack and is not really helpful.

My proposal would be to move displaying of archived cards to the board sidebar similar to how it is done in github projects and trello.

image

This way archived cards would be a separate list just for the archiving purpose and not interfere with the column layout that is just ment for managing currently active cards.

Alternative

So we discussed this recently in our deck design review and came to the conclusion that it might make sense to just have a toggleable additional list in the regular board view for all the archived cards.

cc @jancborchardt @nextcloud/designers @nextcloud/deck

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 does not name files or tests. Start by locating the frontend components that render archived cards and the board sidebar or regular board view; compare the current archived-card grouping with the proposed separate list or toggle. Done means archived cards no longer distort active column layouts and remain accessible through the chosen board UI.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
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.