Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Allow hiding Deck task lists from Tasks while keeping Calendar integration enabled

Aperta
  • Qualcosa non va?
#8,258 0 commenti 2 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
45/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
javascript
Ambito
backend

Direzione di ricerca

Inizia tracciando l'integrazione Calendar/CalDAV di Deck e il modo in cui le sue bacheche diventano liste di attività in Nextcloud Tasks; l'issue non indica file o test specifici. Determina se sia possibile avere impostazioni di visibilità separate o metadati identificativi. Il lavoro è completo quando la visibilità di Calendar per le date di scadenza delle schede di Deck può rimanere abilitata, mentre le liste di attività generate da Deck possono essere nascoste indipendentemente.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.
When Deck's Calendar/CalDAV integration is enabled, Deck cards with due dates can be displayed in Nextcloud Calendar. This is very useful.

However, the same integration also exposes the Deck boards as task lists in the Nextcloud Tasks app, where they appear as lists such as Deck: .

For users who use Deck for project management and Tasks separately for personal or regular CalDAV tasks, this makes the Tasks sidebar unnecessarily cluttered. With multiple Deck boards, a large number of Deck: ... lists can appear in Tasks.

Currently, disabling the Deck Calendar integration is not a solution, because this also removes the useful integration of Deck card due dates with Nextcloud Calendar.

A similar request was previously reported in nextcloud/tasks#2456, but was closed there because Tasks was considered the wrong repository/component for this functionality:
https://github.com/nextcloud/tasks/issues/2456

Describe the solution you'd like
It should be possible to keep Deck's Calendar/CalDAV integration enabled while optionally preventing Deck-generated task lists from appearing in Nextcloud Tasks.

Ideally, Deck could provide separate settings for the two use cases, for example:

  • Expose Deck cards/due dates to Calendar: enabled/disabled
  • Expose Deck boards as task lists to Tasks: enabled/disabled

The desired configuration would then be:

  • Deck → Calendar integration: enabled
  • Deck cards with due dates visible in Calendar: yes
  • Deck: lists visible in Tasks: no

Alternatively, if separating the CalDAV exposure itself is not technically feasible, it would be helpful if Deck exposed sufficient metadata so that the Tasks app could reliably identify and optionally hide Deck-provided task lists.

Describe alternatives you've considered
Disabling Deck's Calendar integration entirely.
This removes the Deck lists from Tasks, but also removes the desired Calendar integration for Deck cards with due dates.

Additional context
The goal is not to disable the Deck CalDAV integration altogether.
The important distinction is between two different user-facing use cases that currently seem to be coupled:

  • Showing Deck cards with due dates in Nextcloud Calendar
  • Showing Deck boards as task lists in Nextcloud Tasks

It would be useful if these could be controlled independently.

Lingua principale
JavaScript
Stelle
1.4k
Fork
358
Merge medio
2g 18h
PR unite (30g)
83

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di nextcloud/deck

Tutte le issue di nextcloud/deck

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.