Due (Deadline) dates
Rhubarb
Design a mechanism that allows to specify when a task is due, as opposed to when a task is scheduled to be done.
Example: Mika's birthday is on July 1st. On that day I want to show up on Mika's doorstep with a present. The
due date
for getting that present is July 1st. But the do date
might be February 3rd or June 29th, because that's when I have time to get the present.Edit: A better name for this feature might be
Deadlines
(see comments below).Edit: Consider adding a separate backlink item for "due soon..." items that shows them x days before the due date. How are other apps dealing with this?
Edit: Consider using
!date
syntax for deadlines/due dates.n
nopi
I bump into this a lot. For me it would be enough to have links to several dates, the last one being the due date. Problem is that the task doesn't show up in the backlinks of all those days except for the first date in the line. (it doesn't matter whether it is the earliest or some other date, the position in the line determines whether it's recognized for the backlink.)
The best for now is probably to copy it as a synced line, use the links to navigate to the three dates and paste the task there. That would also check it off everywhere once done. - No, it doesn't sync that it's checked. Maybe it would without the done date.
It works fine though if I lock in the sync mark (by copypasting a space before the text). Then the check-off is synced to all lines. Having a blue star before the due date is a nice visual, too. That might work for now, will use it a bit. (the [[yyyymmdd]] links are interoperable with Obsidian, so I mostly use those.)
n
nopi
actually, I should put the due date first, then it shows up in the backlink of the most important day. will play with it.
Trisha Cupra
I'd like to see a task that needs to be worked on (or at least reminding you) daily until the due date. So, my current project would be like:
* XYZ Widget project >today...2023-3-03
Anton Sklyar
Just one comment to the other suggestions. Someone mentioned that
>2023-03-01
syntax that we have right now is "scheduled" and that we need a separate syntax for "due".I would argue that current
>
syntax actually represents due date
, because after that date the task is indeed shown as overdue
.Thus, what we probably need is the additional syntax for the
start date
, without changing current behaviour of >
due dates, not to break the existing workflows of the users.This means that
<
or !
syntaxes are not perfect for the feature.Anton Sklyar
How about just a double
>>
for start (defer) date?* Task with due date >2023-01-01
* Deferred task >>2023-01-01
* Deferred and due >>2023-01-01 >2023-01-31
NotePlan could even automatically dim the tasks that have future defer date (i.e.
>>
with future date in it), for the task to be taken out of attention in the project note until it needs that attention.Valentino Serusi
would love start date and deadline
n
nopi
Days with due dates would be nice to display in another color on the small calendar to visualize approaching deadlines, similar to the red days with overdue tasks. If they have a unique syntax such as
!date
this could be possible.
Eduard Metzger
Merged in a post:
Add "Due" panel for tasks!
Pan
Inspired by 2Do, it would be perfect if NotePlan can set the Due date, I think the Due date can be used with the
!
symbol to indicate !2022-02-10
. Does anyone have a better idea💡?Colin Gold
Don’t turn Noteplan into a task manager. Anywhere tasks can remain flexible is a plus, but making tasks have to have a date transforms their flexibility
Eduard Metzger
Looking through my notes I found another syntax idea:
!2021-03-01
= due date, whereas >2021-02-01
would be the start date.J
John Johnson
Eduard Metzger: yeah, I was going to say, if a task has >2022-01-19 it should begin showing up on that day, and persist until completed.
!2022-01-20 wouldn’t be terrible.
But since begin on is >2022-01-18, it would seem natural for due to be <2022-01-20. E.g > is “on or after”, < is “until.”
[ ] develop plan >2022-01-20 <2022-01-23
I realize that could potentially break existing logic.
Hm, what about >= and <= ?
That’s really what they are intended to say, greater than or equal start date, and less that or equal due date. It’s intuitive.
[ ] develop plan >=2022-01-20 <=2022-01-23
Personally, I don’t care for the +5 syntax, as it forces everyone to do date math. If something is due on Feb 12, how many days is that? Also the +5 syntax blends in with the rest of the date, and is not obvious.
Thanks for still considering this, and entertaining our suggestions!
Eduard Metzger
Have merged it with the due dates. Seems to be the same request. I'm not clear how the syntax could look like though. There needs to be something more strict or shorter like
>YYYY-MM-DD+x
, example: >2022-01-19+10
. Means start on 2022-01-19 and due in 10 days?Christian Bogen
Eduard Metzger: Personally I like the !/> notation above better.
Eduard Metzger
Merged in a post:
Schedule task for range of dates (i.e. start and end dates)
J
John Johnson
Such as
Review material >2022-01-04 to <2022-01-11
This would cause the task to appear in References beginning on 2022-01-04 and ending on 2022-01-11
Load More
→