Queries for task management

[Siferiax]

You add :today as input. (:inputs [:3d-after :today] and :in $ ?next ?today)
Then an extra line with [(> ?d ?today)].

[Holanda73_David]

thanks a lot, it worked!!!

[Siferiax]

Sharing my newly complex today query

Tasks for today based on scheduled or deadline

What I wanted was the ability to move a task forward in time through scheduled, but without moving the deadline. However I didn’t want to see these in my tasks for today query anymore. (tasks for today are all those with scheduled or deadline in the past or on today)

#+BEGIN_QUERY
{:title [:h3 " ⚡ Vandaag"]
 :query [:find (pull ?b [*])
   :in $ ?day
   :where
     [?b :block/marker ?m]
     [(contains? #{"TODO" "DOING"} ?m)]
     [?b :block/page ?p]
     (or-join [?b ?d]
       [?b :block/scheduled ?d] ; scheduled on ?d
       (and 
         [?b :block/deadline ?d] ; or deadline on ?d
         (not [?b :block/scheduled]) ; and not scheduled
       )
       (and
         [?b :block/deadline ?d] ; or deadline on ?d
         [?b :block/scheduled ?t] ; and scheduled on ?t
         [(<= ?t ?d)] ; and ?t is less or equal to ?d
       )
     )
     [(<= ?d ?day)] ; ?d is less or equal to ?day, which is set to today.
     [?b :block/parent ?pb] ; the parent of the task
     (not [?pb :block/marker "TODO"]) ; the parent is not a task. I.e. filter out subtasks.
 ]
 :result-transform (fn [result] (sort-by 
   (juxt 
     (fn [r] (get r :block/scheduled 99999999)) ; sort by scheduled, which is substituted by 99999999 when it doesn't exist, meaning unscheduled tasks end up at the bottom instead of the top.
     (fn [r] (get r :block/deadline)) ; and then sort by deadline.
   ) 
   (map 
     (fn [m] (assoc m :block/collapsed? true)) ; collapse the result blocks
     result
   )
 ) )
 :table-view? false
 :breadcrumb-show? false
 :inputs [:today]
}
#+END_QUERY

[Holanda73_David]

hi again,

actually it still shows a task with deadline today.
I tried to see how to exclude but I don’t get it.
Could you help me out?

{:title "📅  NEXT 3 DAYS, NOT TODAY"
    :query [:find (pull ?h [*])
            :in $ ?next ?today
            :where
            [?h :block/marker ?m]
            [(contains? #{"LATER" "TODO"} ?m)]
            (or-join [?h ?d]
              (and
                [?h :block/ref-pages ?p]
                [?p :block/journal? true]
                [?p :block/journal-day ?d])
              [?h :block/scheduled ?d]
              [?h :block/deadline ?d])
            [(and
              [(< ?d ?next)]
              [(> ?d ?today)])]]
    :inputs [:3d-after :today] 
    :table-view? false
    :breadcrumb-show? false
    :collapsed? true}

[Siferiax]

Idk why you made such a weird query
Here’s the query as per my instructions and it works perfectly well.

{:title "📅  NEXT 3 DAYS, NOT TODAY"
    :query [:find (pull ?h [*])
            :in $ ?next ?today
            :where
            [?h :block/marker ?m]
            [(contains? #{"LATER" "TODO"} ?m)]
            (or-join [?h ?d]
              (and
                [?h :block/ref-pages ?p]
                [?p :block/journal? true]
                [?p :block/journal-day ?d]
              )
              [?h :block/scheduled ?d]
              [?h :block/deadline ?d]
            )
            [(< ?d ?next)]
            [(> ?d ?today)]
    ]
    :inputs [:3d-after :today]
    :table-view? false
    :breadcrumb-show? false
    :collapsed? true
}

Here it is a little bit more optimized, but shouldn’t change anything.

{:title "📅  NEXT 3 DAYS, NOT TODAY"
    :query [:find (pull ?h [*])
            :in $ ?next ?today
            :where
            [?h :block/marker ?m]
            [(contains? #{"LATER" "TODO"} ?m)]
            (or-join [?h ?d]
              (and
                [?h :block/refs ?p]
                [?p :block/journal-day ?d]
              )
              [?h :block/scheduled ?d]
              [?h :block/deadline ?d]
            )
            [(< ?d ?next)]
            [(> ?d ?today)]
    ]
    :inputs [:3d-after :today]
    :table-view? false
    :breadcrumb-show? false
    :collapsed? false
}

Both worked in my test environment on iPad version 0.8.16

[Siferiax]

Tasks linked to pages with common tag.

Query all tasks related to one common tag

Here is my pages: [image] [image] Both people and project are linked to one tag work. I would like to gather all tasks from work tag. So I write my journal like this: [image] and then simple query like this works good {{query (and (task doing todo) [[work]] )}} I want to avoid adding all tasks in journal under work tag and write tasks just on first level: [image] and then I would like to query all tasks which related to work but not directly. How can I do it? This seems similar, b…

[Siferiax]

similar to Tasks for today based on scheduled or deadline, but without the deadline and just either tasks scheduled today or not scheduled at all on the current page:

Query to show tasks linked to the current page which have a schedule date of today or earlier, or no schedule date at all

Hi, I created the following query, which works but only shows tasks which have a scheduled date set, but how do I also include tasks that have no scheduled date at all? #+BEGIN_QUERY {:title "Tasks" :query [:find (pull ?b [*]) :in $ ?current-page ?today :where [?p :block/name ?current-page] [?b :block/refs ?p] [?b :block/scheduled ?d] [(<= ?d ?today)] (task ?b #{"TODO", "DOING"})] :inputs [:current-page :today]} #+END_QUERY Any input would be helpful. Thanks! …

[logseq-lion]

Hi, is it possible to for any of the queries in your OP to generate a table view of all my tasks with columns for project, deadline, priority, etc? Then can I filter and sort this table by the column values? Thanks in advance!

[Siferiax]

This is partially possible and depends on what you are looking for exactly.
For example the query under the header

@Siferiax

Tasks with their page name

Generates a table. See the :view part of the query.

Please post some example data and desired result and I’ll have a look!
Do be aware that you will not be able to filter and sort the table by the column names though. The query will just give you a static result.

[Siferiax]

@Siferiax

Tasks with their page name

A little bit more of an advanced query, using a view to make a table of the page name and task.
It will get rid of the checkbox unfortunately, but the task is clickable to navigate to it.

Coming to simply queries:

Add pagename field to the list of table fields in simple query

This feature landed with Enhance: Add page column for query tables with block results by logseq-cldwalker · Pull Request #8869 · logseq/logseq · GitHub and is going out with the next release

[Viraj]

Hi, this has been such a useful resource. Thank you!

I am starting with your “Tasks without a specific page link” and modified it a bit. I have breadcrumbs as false but I still end up getting the references for the tasks that I am pulling. Here is the code that I have

#+BEGIN_QUERY
{:title [:h3 "Tasks without page reference" ]
 :query [:find (pull ?b [*])
   :where
     [?p :block/name "habit-tracker"] ; name is always lowercase
     [?b :block/marker "TODO"]
     (not [?b :block/scheduled])
     (not [?b :block/deadline])
     (not [?b :block/refs ?p]) ; we cannot use not until we have specified the variables used in it
 ]
   :table-view? false
   :breadcrumb-show? false
}
#+END_QUERY

Can you please help to avoid having all these references, so that I can just a list of things?

[Federico_Frosini]

You need to add

:result-transform (fn [result] (sort-by (fn [r] (get-in r [:block/created-at])) result))

Just after

:table-view? False

[Siferiax]

To add to @Federico_Frosini answer, any :result-transform works for this.
So something as simple as :result-transform (fn [result] result) also works.

[logseq-lion]

Here’s the example I have in mind - I am wondering if I can get columns for project, priority, deadline, and scheduled?

Query:

#+BEGIN_QUERY
   {:title "🟠 SLIPPING"
  :query [:find (pull ?b [*])
          :in $ ?start ?today
          :where
          (task ?b #{"NOW" "LATER" "TODO" "DOING"})
          (between ?b ?start ?today)]
  :inputs [:-7d :today]
  :result-transform (fn [result]
                      (sort-by (fn [h]
                                 (get h :block/created-at)) result))
  :collapsed? true}
#+END_QUERY

[Viraj]

Post 0.9.2 update, all my queries have gone back to show references and they are no more a list of TODO things. Did others also face similar issues?

[Siferiax]

I believe this is a solution for the issue: :result-transform and grouping of results · Issue #6641 · logseq/logseq · GitHub
Which a lot of people have asked for / complained about. (myself included lol, even though I often used result-transform to get rid of it)
There should be a way to remove the grouping, but I’m unaware if this is now available or not.
Created a feature request topic for it:

Option to disable query block grouping for specific queries

In Logseq we could add a :result-transform to queries to remove the default group by page. In many situations this was undesired behaviour, but in others it was exactly what was intended. In Logseq 0.9.2 this was fixed and the default group by page is now displayed regardless of the use of :result-transform. This is nice! But it would also be nice to have the option to disable this grouping behaviour for people who were using the :result-transform to remove it. For example if I have several …

[Federico_Frosini]

Thanks for the info.
I have problem also with :collapsed? Function.
Do you have any idea and solution?

Thanks

[Siferiax]

From what I read about it, seems that’s an actual bug. So would need a bug report I guess.

[Federico_Frosini]

ok. I hope the fix it quickly.
Everyone is talking about it even in discord.