nextcloud / nextcloud/tasks

[Feature-Request] Additional Scheduled Date

Open
#2,941 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
JavaScript
Stars
706
Forks
117
Avg merge
8h 50m
Merged PRs (30d)
18

Description

Is your feature request related to a problem? Please describe.

Currently, the Tasks app allows setting a start date and a due date for tasks. However, this can make it difficult to plan when I actually intend to work on a task. A task might be due next week, but I may want to schedule it for tomorrow to ensure I complete it on time. Without a separate scheduled date, it’s hard to distinguish between when a task becomes available (start date), when I plan to do it (scheduled date), and when it must be completed (due date).

This makes day-to-day task planning and prioritization less efficient, especially for users who follow time-blocking or scheduling-based productivity methods (e.g., GTD, timeboxing, etc.).

Describe the solution you'd like

I’d like to have a scheduled date (or planned date) field for tasks, in addition to the existing start and due dates. This field would represent the day (and optionally time) I plan to work on the task. The selection of the day and the time can be implemented analogously to the time selection for the start and due date. It would also be good to provide filtering and notification options just as for the scheduled and planned date

Describe alternatives you've considered

Using the start date as a scheduled date — but this conflicts with its intended meaning.

Additional context

No response

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 locating how the Tasks app currently handles start and due dates, including date/time selection, filtering, and notifications. Clarify the semantics of a scheduled or planned date and how it should interact with those existing fields. Done means the new field and its requested filtering and notification behavior are consistently defined across the task experience.

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
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.