Logseq’s current task management is best in class for the new generation of networked knowledge managers, but one thing I think would make it better is the ability to apply some of these task management features at the page level (rather than just to blocks). My idea is to be able to mark pages with TODO/DOING/NOW/LATER markers just like task blocks. Together with my other request to have a Page Specific NOW section, I think this would enhance the way task management works for complex projects.
Hello and thank you for this request.
I am specifically interested in topics around task management, because that is also my main usecase with Logseq.
May I briefly explain how I currently handle it:
For each major task I create a separate tag in the form
Since each tag also has its own page, there is also a page for each major task.
On this page I have the following structure as content:
[#C] #BACKLOG.task description (what is the task about)
Info / Links
- some infos and links regarding this task
- TODO Name → do something
- TODO Name → so something else
- ┤date├ detailed infos about what was going on over time
- Info / Links
What do I do, when this task has been completed? → I rename the page (the tag) and replace the word “task” with “done”.
This renaming has the effect that when searching for tasks (“open tasks”), these entries no longer appear and wherever there was previously #task.xyz, there is now the tag #done.xyz - a clear indication that this task has been completed.
So I mimic something like you requested - I coded the state of the task/page into the page title. Starting pages with “task” or “done” is something like your request to mark whole pages as TODOs.
I’m not sure I’d prefer that. Because then there is a mixture between todos as individual steps to a task/project and the status of the task/project itself. A query for open todos would then perhaps return both open projects and open individual tasks.
But perhaps this problem could be solved simply by defining a separate workflow (separate status definition) for the status of the pages. Something like what is generally suggested here:
I find the suggestion really interesting (even though I currently have a different solution) and am curious to see if there will be any progress on this.
Perhaps one more comment on
As you can see from the structure above, I have specifically grouped all todos in one section. For the task management of projects I have deliberately decided not to distribute the totos of projects arbitrarily.
I handle this quite differently than in the journal, where information that accumulates throughout the day is mixed with small todos and where the journal queries are very important for me.
I hope this has helped to get the discussion going.
This is doable today using page properties.
I am currently working on something like that:
With the properties you can say that a page is a project, and that it is active or not (or now, later).
I use a template to add the properties:
template:: project category:: projects status:: #Completed [[🗄 Archives]] [[Active]] [[Someday/Maybe]] [[Later]] area:: goal:: related-to:: tags:: time-investment:: reward:: impact::
Yes, it is doable, but Logseq already has built-in task management features for blocks, so why not extend these to pages as well? It will allow for tighter integration between the two, and I don’t see any down sides?
I agree with you on that. Projects should be first class citizen
That looks very interesting and just what I have been looking for.
As I am quite new to Logseq and has not gotten to grips with its query system, use of page properties and page tags yet, could you please post an example page of how the properties and tags have been implemented?
Also, are all the properties in your table fetched from the pages directly, even the status (as it seems you actually define the options directly in the template, which I assume would not be needed if fetched from each page)?
You can see my workflow here: