nextcloud / nextcloud/deck

Due date linked to Nextcloud built-in calendar

Open
#4,451 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

IDEA

While creating a card, set the due date/time in the right hand panel and saved it, although it's nice to see it both in the Nextcloud dashboard Deck widget as an upcoming card as well as an upcoming card in the Upcoming cards section in Deck, it would be nice to have this card created in the Nextcloud built-in calendar as an event (based on the due date/completion time already saved).

So for instance: I create a card in Deck with all its details and I set a due date as 15/02/2023 and save the card. After that, this card appears as an event in the Nextcloud built-in calendar.

--

Along with that it would be also nice to have the possibility to set a notification via email (in Deck at the time the card is created) which gets saved in the calendar event within the Nextcloud built-in calendar. By doing that, the user will be informed by the Nextcloud calendar and that will help to complete his task.

I added a screenshot below which shows how this card could appear in the Calendar:

image

My apologies if this topic was already opened but I couldn't find it.

Thanks in advance.

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

The issue names no files, tests, or entry points. Start by locating how Deck saves card due dates, then trace the integration boundary with Nextcloud Calendar and notification handling; done would require an agreed scope for calendar events and email reminders, plus tests for the resulting behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
api, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.