Having tried the DB Demo, I'm a little concerned about task tracking

This isn’t meant to be disparaging or discouraging, I believe in Logseq and the devs. It’s an amazing app. I love it and trust DB can be amazing with time, but I do think it’s going to take some time.

I’ve seen a few posts now about folks growing impatient waiting for DB. Well, I’d like to say the opposite. While I’m excited about the potential promises of DB, I’m quite concerned about the UX of it as it stands, and would much rather the devs take their time to iterate and refine all of their new ideas.

I’m particularly concerned about the new UX of task tracking. TODO/DOING/DONE was extremely elegant, but the new approach seems a bit complex and clunky. Curious how others feel about these changes, or if I need to change the way I think about it (as logseq forced me to do when I first adopted).

What is the new approach? Why is it clunky?

1 Like

I see you deleted your post, but thank you for providing info on how to modify statuses to bring the terminology back towards my comfort zone! As you can imagine I still struggle with the new workflow and miss having the text next to the checkboxes.

I have deleted my post ‘cause “status” is a built-in property so you can’t delete preset values, but you can add new values

When you use the keyboard shortcut CMD + ENTER or CTRL + ENTER, it will cycle through the task status: TODO/DOING/DONE only, just like in MD mode.

logseq-db-task-status

3 Likes

Do you mind to share your logseq settings? , I really like your setup

That’s super cool, I had no idea. Thanks Danzu!