I’ve been using Logseq for quite a while now and love it, however I’m kind of stuck on something in my process. When I work on something at my job, I’m often working on it for multiple days. How does anyone here capture that?

Do you do something like this?

[[figure out how to create x]]  
  - item 1  
    - subitem 1  
    - subitem 2  
  - item 2  
[[change out every y in all of the zs]]  
  - action 1  
  - action 2

The thing is, I can then go to each one of those as a page and see everything, but I can’t add to it for that day. I can just start the next day with an entry of [[figure out how to create x]], but I won’t be able to see the whole thing while I’m doing it. I also won’t be able to add something in context, like this without removing it from the day I’m working on it:

[[figure out how to create x]]  
  - item 1  
    - subitem 1  
      - subsubitem 1  
    - subitem 2  
  - item 2

I see that you can copy and paste block refs, but that largely is the same thing as a page.

Do any of you deal with this? Should I not be so concerned about keeping my edits for the day?

  • strg_y
    1·
    7 months ago

    I am also trying to pin down the right workflow of how to track projects and tasks, information over a period of time.

    At the moment I reference the project in the daily journal where I add sub bullet points of what happened that day.

    So you could in reverse see a history in the projecs page.

    I always liked the way loqseq organically builds up a network of information. But I actually dont use logseq at the moment, instead obsidian is my main pkms. There I have seen workflows where you move open tasks or items from day to day. But I’m not into that.

    • Ken Oh@feddit.onlineOPEnglish
      2·
      7 months ago

      I think referencing the project for the day might also be the way to go. I’ll just have to flip to the page if I want to see more.

      Actually, I just had this idea, opening the project page in a sidebar is something I should look into doing.