nextcloud / nextcloud/deck

Toggle tasks visiblity board independendly

Open
#3,477 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop enhancement feature: dav integration: tasks / calendar
Dominant language
JavaScript
Stars
1.4k
Forks
354
Avg merge
1d 10h
Merged PRs (30d)
43

Description

I am unable to find this option or it just doesn't exist. Eitherway, it would come quite handy to turn off the visibility inside tasks for several board. Some oards are maybe not meant to get done any time soon, because they're more like a persistent library ( sorry to everyone if this is not the intended way of using deck, but i am glad Deck exists). Then it actually not usefull for them to show up inside tasks where I am also unable to find such an option. So it shows up in the "All" section..

There is "Turn off die date reminders", but there should also be "Turn off tasks/calendar visibility".

Edit:

Eventually, but this might be too explicit, it might be even usefull to "mute" individual lists
One could just create a new Board with desired Tasks, if "only" boards could get this feature, but because you can't intuitively "drag'n drop" between boards, this is not a time-consumption-minimizer option in some cases. #3478

Because inside Tasks you neither can delete Deck lists, nor can you set a Deck List as the Default List. Only Calendar created via the calendar app can be used as the default.

I dont know if its on Decks or Tasks side why its not possible to create new Tasks via Tasks... I dont get this crossover. #1878

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 the related context in issues #3478 and #1878, along with the Deck/Tasks crossover described here. Clarify whether the intended scope is board-level or list-level muting, then verify the chosen visibility behavior across Tasks and Calendar.

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
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.