nextcloud / nextcloud/deck

STATUS field instead of using multiple lists (again and again)

Open
#5,791 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
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.

As is

Today Deck uses multiple lists (e.g. open / in progress / done) to reflect the status of the card.
The disadvantages are, that

  • those lists are usually again and again created for most boards.
  • the semantic status is not captured (instead it is hidden in the name of the list, e.g. open)
  • the overview shows the different status lists multiple times, because it "does not know about them"

Describe the solution you'd like

I would suggest to have a "status" field available, that allows to flag (e.g.) open, in progress, done.

At best, the list of statuses would be configurable (even per board) (e.g. open, in preparation, in progress, done). But the basic set above would be a very good starting point.

Having this, the deck views would nicely allow filtering for this.
Additionally, setting the status could be easily done by dragging between the columns in a respective "status view".

Already discussed?

I wonder why this request is not yet already on the issue list, at least I did not find it.
Please let me know, if this was already discussed and excuse that I did not find / refer to it.

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 reviewing how Deck currently represents cards across multiple lists and how its overview handles those lists. Done means a status field supports the proposed statuses, can be configured per board, enables filtering in deck views, and supports moving cards between statuses.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.