nextcloud / nextcloud/deck

Allow to filter upcoming cards

Open
#6,453 2 comments 7 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature: filter feature: upcoming cards needs discussion
Dominant language
JavaScript
Stars
1.4k
Forks
354
Avg merge
1d 10h
Merged PRs (30d)
43

Description

At Nextcloud we use Deck a lot. This means that I not only have my own boards but many boards shared from colleagues. Many of them are just shared with me "for my information" or for occasional collaboration. But the board fills up my "upcoming card" view with so many cards up to come and overdue cards that I can't use it to keep an overview over my boards and the cards and due dates I really care about.

Possible solution:

  1. Filter option on "upcoming cards" so that I can hide the boards I don't care. Filter should remember the last setting so that I don't have to apply the filter again and again.
  2. Introducing a setting per board and user, similar to the "due date reminder" setting, allowing the user to define board by board if it should show up in the overview or not
  3. Reuse the existing "due date reminder" setting and assume that when people don't want to get notifications for boards, they also don't want to see the cards on "upcoming cards" as they don't care about the deadlines.

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 locating the upcoming cards view and the existing per-board due date reminder setting. Compare the three proposed approaches and confirm the intended behavior with maintainers before choosing an entry point. Done means users can exclude selected boards from the overview and the choice persists as specified.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
backend, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.