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?

  • INeedMana@piefed.zipEnglish
    2·
    3 days ago

    I’m not sure I exactly grasp what you mean. But if I do, I’d do it like this

    Create file projects/x/item1/subitem1/subsubitem1
    Inside add a header on top with a ref to date of work

    # [[2025/07/03]]  
* that way when you open the file, you see the most recent note  

# [[2025/07/02]]  
* bar  

# [[2025/07/01]]  
* foo

    That way, using hierarchy and references parts of 2025/07 or projects/x you can see what you were working on in that month or how did the whole flow for an item go

    Does that address your issue?