I’ve been moving back and forward between Logseq and Obsidian, and one thing really stops me from committing to Logseq,… this feature request.
What’s fundamental to both is that my data is locally stored and I can work with no internet connection, and that data is in a format I can utilise elsewhere. Task Management is a key activity for knowledge workers, and for me it’s crucial.
Earlier in this very thread, here, Aryan, shares a Logseq plugin that comes some of the distance, but doesn’t fully close this loop for me. It may be enough for others, but I suspect there is a substantial number of others here that really want their own workflows, in their phraseology, to be easily implemented in Logseq.
My feeling is that this should be in the product out of the box. Much the same as every other person wanting their feature native to the product But I recognise that my priorities and needs may not be the same as those who get to control what is given time and effort.
All the knowledge workers I know have more than one distinct workflow. The two workflows I described at the outset of this thread, are (almost) still the same.
'((sequence "BACKLOG" "TODO" "INPROGRESS" "PENDING" "ONHOLD" "|" "CANCELLED" "DONE")
(sequence "REPORT" "BUG" "KNOWNCAUSE" "|" "NOTFIXING" "FIXED")))
Using block properties kinda works, and if there was a plugin (perhaps there is?) that would allow me to manage tasks using block properties, then that might remove the final amount of friction here for me.
It could be a plugin that:
- uses a block property
status (or similar)
- we’d need someplace to specify the workflow sequences
- the order of statuses in each sequence
- for each workflow, which statuses are ‘open’ statuses, which are ‘closed’ statuses
- set a keyboard shortcut that would cycle the statuses for the current task, through the values in the sequence for the workflow in use (happy to keep statuses globally unique as this keeps it easier for humans to both know where in a workflow a thing is, and which workflow it is in)
- ideally a
shift-<keyboard_shortcut>` would cycle in statuses in reverse order (or separately definable)
- bonus would be to track total time in each status (I’ve not need to keep an audit of when it switched back and forth
Thusly, if there isn’t going to be any communication from the developers, either via this thread, the roadmap, or via git issues, then are there any plugin developers interested in discussing this further?
Specifically, I’m curious to know how much time/effort you’d feel is involved in achieving the above.