nextcloud / nextcloud/deck

Calendar integration: Assign Calendar time to Deck card and vice versa

Open
#3,295 5 comments 11 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

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.
Not a problem - an optimization. I would like to simplify time management/scheduling workflows and stats/report generation.

Describe the solution you'd like
I would like to suggest a direct integration between Calendar and Deck which allows the user to directly assign/link calendar times to deck cards.
E.g. when creating a new calendar time, there could be a field "Assign to deck card" which allows to pick from a list of cards. Ideally this list of cards could be filtered e.g. by board, column or "assigned to me". Also, in a deck card, there could be a link "create new time" which would lead to creation of a calendar entry for that card.
Cards would have a tab which displays all assigned calendar times.
The goal would be to simplify the scheduling workflow as well as make it easier to generate time statistics through external tools.

Describe alternatives you've considered
At the moment I'm manually entering references to cards into calendar entries but that's a little cumbersome and also relatively hard to filter when trying to generate stats or reports. It also only has references from calendar times to deck cards but I can't see any Calendar assignments in Deck.

Additional context
N/A

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, so start by mapping how Calendar events and Deck cards are represented and linked in this repository. Done should cover assigning existing events to cards, creating an event from a card, viewing assigned times on cards, and the proposed filtering options.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.