As not all tasks are finished on time it would be valuable to have the done date added to the DB schema of logseq.
One could activate the timetracking feature of logseq to get the latest date tracked (See a query @darwis made here. But that is not something I really need. But I would like to know when a task is done.
I am not entirely sure how the DB schema works exactly but I see that there is a
:block/marker "DONE"}
entry in the block data. If also a :block/marker/done “DATE”} part could be added to store the datetime of the moment a task is set to done that would be great.
I have no idea if it workes like this. Feel free to adjust conform working standards.
If this date could be added to be visible at the moment a task is set to DONE that would be great. So you see in one glance when a task is finished. Currently that is not possible with using the timetracking feature. And I have no need for that.
An extra reason to do not use the timetracking feature as I have tasks that directly go from TODO to DONE without the DOING step. Not sure how timetracking works in that scenario.
Maybe a same logic as with scheduled and deadline might work also. So in the :block/content
Not sure what the consequences are in terms of presentation, quera-ability, ect.
Thanks! I’ll be merging the two threads you linked, but not with this post itself as their scopes are a bit different. The other two posts explicitly expressed a wish to link to journals in the bidirectional link format, while this post suggests it may be accomplished via some means similar to scheduled and deadlines (for example something similar to CLOSED: <timestamp> in org-mode, I think).
I’m also interested in this functionality. I like to use my journals for daily standup meetings and a query that returns “completed yesterday” tasks would be very helpful
I had a goal to create a task list that displays either unfinished tasks or tasks completed no earlier than yesterday. I didn’t like that completed tasks immediately disappeared from the list, and you couldn’t see what was done today, depriving you of the satisfaction.
I realized that Dmitry Dushkin’s plugin doesn’t work quite right. It creates a date in the format [[PreferredDateFormat]], but Logseq doesn’t perceive it as a link to the daily log without additional manual editing.
Moreover, it’s inconvenient to work with such a date format. I made some edits so that it always sets the date in the ‘yyyyMMdd’ format. This is the format in which Logseq itself handles dates, including how variables like :today are stored.
And it all works now. Additionally, I hid the “completed” property in Logseq settings, so it looks like it was out of the box.