Add a done date to done tasks that is query-able

JeRoen · February 2, 2022, 3:14pm

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.

waynegong · May 30, 2022, 8:35am

+1

I want query my task with done date

John_Doe · April 20, 2023, 8:27pm

It would be great feature.
People keep asking it Query for Tasks done today - #6 by John_Doe

With this feature we can see what was done this day/week/month.
It will allow to build DONE table in kanban board to see progress.

Luhmann · April 20, 2023, 11:14pm

I think there are a number of related feature requests, would be good to gather them all together. Here is one I found:

https://discuss.logseq.com/t/automatically-record-date-when-completing-todos-via-query-in-the-daily-journal/14166

Luhmann · April 20, 2023, 11:15pm

And another one: Add date and reference after DONE

bigDaddy · April 21, 2023, 1:07am

Task completion plugin

WQing · April 21, 2023, 1:17am

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).

John_Doe · April 21, 2023, 6:44am

It does not work correctly, see my FR Please change timestamp format to, e.g., 20230306 · Issue #10 · DimitryDushkin/logseq-plugin-task-check-date · GitHub
There are some other plugin which might help.

But it seems like queering all DONE tasks should be the core functionality, so would be great to have.
Thank you.

Luhmann · April 21, 2023, 9:15am

Note that this plugin is no longer being maintained. There is also an issue with querying the completion date that was never resolved.

Luhmann · April 21, 2023, 11:08am

UPDATE:: I think the issue (with needing to reindex before querying property dates) may have been fixed?

frebtherat · May 12, 2023, 1:20am

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

Soloqub · January 28, 2024, 7:15pm

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.

uclguto · September 30, 2024, 7:03pm

@Soloqub Could you share this solution? I really need to know when did I finish my tasks

Soloqub · September 30, 2024, 7:57pm

@uclguto
Yes, sure, here it is.

cldwalker · January 23, 2025, 2:56pm

In the db version, each status change is recorded and queryable. In other words, done and any other status state have a timestamp. Docs have been updated to mention this - docs/db-version.md at feat/db · logseq/docs · GitHub

txp · January 26, 2025, 7:05pm

@cldwalker I experimented with the DB version (both on test.logseq.com and a self-built version on my laptop). After marking a task as “done,” I can see the “Status history” with an entry like “Done 2025-01-26 17:34” when I click on the time indicator.

So far, so good. However, I can’t figure out how to access the “Status history” with an advanced query. In fact, I’m not even sure what the variable name for “Status history” is, because it doesn’t appear in the (Dev) block data. Have the advanced queries gone through any major changes in the DB version? I’m completely lost with advanced queries today— even some minimal examples aren’t working anymore.

Can you, or anyone else, provide a small advanced query example to retrieve the “Status history”? It doesn’t have to be anything fancy; I just need to get some kind of result back as a starting point for further experimentation. This would be greatly appreciated!

cldwalker · February 4, 2025, 10:02pm

Advanced queries have gone through some changes. See docs/db-version-changes.md at feat/db · logseq/docs · GitHub for some tips. Feel free to send a pull request as you or others come across more changes.

The following advanced query returns task status and its timestamp for a block “b1”:

[:find ?status-title ?created-at
 :where
 [?b :logseq.property.history/block ?bl]
 [?b :logseq.property.history/ref-value ?status-value]
 [?status-value :block/title ?status-title]
 [?b :block/created-at ?created-at]
 [?bl :block/title "b1"]]

Unfortunately this advanced query can’t be rendered in app yet so this is only queryable through scripts. If you’d like property history to be queryable in app, feel free to create a post in the discord #alpha-db-feedback. Here’s what this query looks like for a block that has had four different status states:

txp · February 9, 2025, 10:12pm

Thanks for the example, @cldwalker! I was already interested in exploring the scripting capabilities of database graphs…

I’d love to be able to query property history within the app, but unfortunately, I’m still on the waiting list for the Logseq DB alpha tester program, so I don’t have access to #alpha-db-feedback.

Hopefully, someone else will create a post about it.