Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#8,258 0 comentarios 2 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
javascript
Área
backend

Línea de trabajo

Empieza por rastrear la integración de Calendar/CalDAV de Deck y cómo sus tableros se convierten en listas de tareas en Nextcloud Tasks; el issue no especifica archivos ni pruebas concretos. Determina si es viable contar con ajustes de visibilidad independientes o metadatos identificativos. Se considera terminado cuando la visibilidad de Calendar para las fechas de vencimiento de las tarjetas de Deck puede permanecer activada, mientras que las listas de tareas generadas por Deck se ocultan de forma independiente.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
JavaScript
Estrellas
1.4k
Forks
358
Merge medio
2 d 18 h
PR fusionados (30 d)
83

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de nextcloud/deck

Todos los issues de nextcloud/deck

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.