[Feature-Request] Additional Scheduled Date
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- full-stack
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.
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
- Dominant language
- JavaScript
- Stars
- 710
- Forks
- 125
- Avg merge
- 19h 37m
- Merged PRs (30d)
- 12
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nextcloud/tasks
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
nextcloud/tasks#3240 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
nextcloud/tasks#3111 · 1 comment ·
Maintainers usually reply within 1 day
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
nextcloud/tasks#122 · 9 comments · 25 reactions ·
Maintainers usually reply within 1 day
-
1. to develop
Difficulty 5/5 Over a week Newbie friendliness 39/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
remotion-dev/remotion#13341 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
svix/svix-webhooks#2808 ·
Maintainers usually reply within 1 day
-
enhancement should-have ux
Difficulty 2/5 1-3 hours Newbie friendliness 72/100