Add optional time in addition to date to "due"

[schemar]

[bikingbadger]

Would this be to also then somehow have a reminder pop up?

[schemar]

Nice, thank you!

I think even now you could combine them. The notification date is not necessarily the same as the due date, for example. Maybe you want to be notified two days before the task is due and so on.

[wenlzhang]

Thanks for the hint!

I tried to define a task like the following, and it worked:

- [ ] Task #Reminder (@2021-08-28 12:00) #Task #Life 📅 2021-08-30

With settings like the above, I aim to achieve the following:

• One can see which tasks managed by Tasks have reminders by checking the tag #Reminder.
• This task belongs to the category #Life.

One drawback with this setting it that the task description becomes too long, with the actual task content being only "Task". 😅 Regarding this point, maybe the following issue is related:
Have a "short" mode which shows emoji details only on hover · Discussion #108 · schemar/obsidian-tasks

With sorting by priority, due time, etc., supported in the future, Tasks would become even more powerful!

[wenlzhang]

Just want to let you know that the Reminder developer is planning to support Tasks style tags:
uphy/obsidian-reminder#10 (comment)

[schemar]

Thanks!

[imed-ghomari]

Reminder does work with Tasks, but only in this order name of task + reminder date + recurrence + due date. Also, there are 2 problems :

• When you complete the recurrent task in preview, the reminder date doesn't follow the recurring interval
• The notification include name of task + recurrence + due date instead of including just name of task

[ryanmsnyder]

I would like to see this too so that Reminder can pick up Tasks' due date and time and automatically remind you based on that due date/time.

Right now, Reminder has an option called "Distinguish between reminder date and due date" and when you turn it off, it will automatically use Tasks' due date as the reminder date rather than needing the additional clock emoji ⏰. However, since Tasks doesn't support time, Reminder will default to its "Reminder Time" setting.

Maybe this feature request is better served for Reminder rather than Tasks. However, this would simplify things a bit for people that are ok with their reminder and due date being the same (i.e. I set a due date 📅2022-08-01 11:00AM and Reminder automatically notifies at that date and time). Since there are already so many potential emojis/options for a task, it would be nice to eliminate the need for an additional emoji (⏰).

[zhcqiu]

We all need adding optional time!!!

[Cito]

I disagree that "we all need this". If you manage your todo items GTD style, everything that has a fixed time should go into "The Calendar as Hard Landscape", where you manage your time blocks. You only use Tasks to enter the todo items and keep track of them in various lists (views).

That said, I agree that better integration with the reminder plugin (or implementing reminders in Obsidian Tasks itself) or with calendards can still be useful, and for that we would need to support time,

[claremacrae]

We all need adding optional time!!!

I know you maybe didn’t mean it like this, but please understand that this plugin is entirely written and maintained by volunteers, and we have a finite amount of times in our days too.

People demanding functionality - especially in multiple tickets like today - and not contributing is very demotivating.

[pm64]

Would it be appropriate to move this back into Issues? Putting aside the urgency/priority, I think the requirements here are well-understood.

[claremacrae]

No, there's no need.

I do look at both this category in Discussions and Issues when considering what things I feel like working on.
There are way, way too many Ideas under Discussions for it to be worthwhile moving them to Issues/Feature Requests.

Also, moving them would lose existing votes, of which this has a reasonable number.

[pm64]

Also, moving them would lose existing votes, of which this has a reasonable number.

Especially if you count votes in all of the dupes: #668 #292 #69 and #323

Greatly appreciate all you do @claremacrae!

[claremacrae]

Just to note that in a duplicate request, I pasted in a list (most) of the steps required to implement this:
#2394 (comment)

[claremacrae]

I'm closing this in favour of #668, because it covers a broader range of fields, and it doesn't divert in to different bodies of work like notifications.