nextcloud / nextcloud/deck

Allow select or filter of boards in the upcoming card view

Open
#5,515 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature: filter feature: upcoming cards
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.
The upcoming card view is very powerful as long as there is consistency in the way you deal with cards. I am a member of 50+ boards. Some of them follow a precise logic, some of them follow a different logic, and other don't follow a specific logic at all. ATM I kind of frustrated, because I have no options to remove boards from the upcoming card view, and boards with different logics are mixing up, making it very difficult for me to manage the cards.

Describe the solution you'd like
A first quick approach could be a list with a select option: select all boards you want to appear in the upcoming card view (or unselect all boards you don't want to appear in the upcoming cards view).

Describe alternatives you've considered
A most advanced appraoch could be to have a kind of a view feature for the upcoming card view. You could create a view, and select which boards should appear in the view.
You could have as many views as you need.

Additional context
Some examples about the different contexts I have in my case:

  1. I am member of boards used to track customer projects (one board per customer, ~30 customers)
  2. I am member of boards used to track events, board is managed by the marketing team, but I don't need to deal with these cards in my day to day routine
  3. I am member of boards used to track team activities, but I don't need to deal with these cards in my day to day routine
  4. I have a board I use to track profesional journeys, and expense reports.

Mainly I'd like the upcoming card view to be cleaned up from 2,3 and 4.

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 at the existing upcoming card view entry point and trace how boards are loaded and displayed. Compare the simple board-selection request with the alternative saved-view idea before choosing a scope. Done means users can control which boards appear in the upcoming card view and the selected behavior is covered by the project's relevant checks.

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.