[Learn Log] Using Logseq for task management and managing task queries!

I’d like to get better at using Logseq for task management and have it function as my single inbox for ToDos.

Today my ToDo list is made up of a broad variety of tasks. Some have very specific “deadlines”. Other’s are “someday”. Many are associated with specific projects. Some are even not my tasks at all but something that I’m waiting on someone else so that I can get unblocked.

Since I put everything on the journal page, most built-in queries and journal tools “schedule” these tasks for the day I enter them, not the day that I need them done by. Many of my tasks don’t have a specific due date so I’d like to assign them a deadline of “#someday”. I’ve tried creating my own task template and writing my own queries, but so far task management isn’t working for me.

As a secondary goal, I’d like to develop a best practice for taking notes when I DO get around to working on or completing a task. Often I’ll give myself a task to to read or watch something on a given day’s journal page. When I get around to watching/reading the thing, I tend to take my notes in a sub-block under the task. Anecdotally I’ve found that I never come back and look at this stuff (or struggle to find it when I want it). Curious if other people have better workflows.

Finally, I’ve spent TONS of time trying to write advanced queries and find them really difficult to troubleshoot when they don’t work as expected. I’d like to understand if would be possible to create some kind of a datalog/datomic query “debugger” that would allow a user to inspect the result at each step in an advanced query. I think this would really open up the power of Advanced Queries for logseq users!

2 Likes

Awesome start of your learn log, JP!

I’m happy to see we have very similar goals. I also want to build better task management workflows with Logseq, and I want to nest my notes underneath the task itself. I already have some possible solutions in mind, which I’ll share soon in my learn log.

Are you able to share some screenshots? Maybe blur out some of the text itself (but please show any links or tags). That’ll help me and others to give better suggestions on how to structure your notes and queries.

What tags/links do you add to these notes? And do you have a use for your notes in the future, for example, to get something done? Screenshots would help here as well.

This is really good product feedback, thank you. I’ll send our developers a link to your post.

Seeing where things go wrong in your query would definitely help the learning process. Short feedback loops = faster learning.

1 Like

Nice to hear that we share the same goal and struggle together with advanced queries :wink:
I just put my getting things done implemenation in the forum, it might answer some questions how to structure things:
Query: How to sort todos by page reference with certain tags (GTD) - Questions & Help - Logseq

Ideally I want to

  1. input daily in journal as inbox, example:
    /WAITING [[ImportantProject]] ask #BobFromMarketing for the TPS report.
  2. Browse by project as one dimension
  3. or context (e.g. a person or a place) as another dimension on the same task.

The context simplifies getting things completed because e.g. before a meeting with Bob the tag #BobFromMarketing shows me all tasks for which I need his input over all projects he is involved in.

4 Likes