It actually works in the terminal. Really its a nodejs repl. I have the task logic and the repl stuff seperated out so that I'd one day be able to make it web based.
You should try it. There's no one right way to use it. The commands I use most are pull() aka p(), r() rank with short ids, pullmirror() aka pm() gives you a sample of past tasks to see if you want to do them again or re-add them to the main stack, addfromfile() let's you bulk add from a file(), add() open a prompt to add tasks directly, remove(), done() remove and mark done using long id, d() mark done the task you ranked top in your last ranking or use short id, search() look if a task is present, pullexposed() pull but only consider tasks that have ranking data, edit() edit the text of a task, lookback() look at what tasks you have gotten done either that day or some number of days back.
I tend to do three rankings and then do the top task of the third ranking. I find that helps me and it identify what's actually high value without getting slogged by a huge list.
It also supports "users". Basically separate list. Like I have a Sunday list for all the fun stuff I want to do. Or if I have some majorly large task I'll spend 10 minutes dividing it down to the smallest tasks possible and then spin that off to its own user and work on that for half a day. That's rare, but if I have a single task that takes half a day it's nice. That means I can have stretch goals accumulate in the same list and then migrate them back out to the main list to follow up with some stretch goals against some of the other things I need to do.
Log in
Neat that you have a git lab.
Does that task management thing work in browsers or is it an app?
I've only ever used .txt files, simple and universal, usually with an outliner that has collapsing sections (to conserve visual space).
Looking forward to trying the HumHub toys like tasks, calendar, etc.
It actually works in the terminal. Really its a nodejs repl. I have the task logic and the repl stuff seperated out so that I'd one day be able to make it web based.
You should try it. There's no one right way to use it. The commands I use most are pull() aka p(), r() rank with short ids, pullmirror() aka pm() gives you a sample of past tasks to see if you want to do them again or re-add them to the main stack, addfromfile() let's you bulk add from a file(), add() open a prompt to add tasks directly, remove(), done() remove and mark done using long id, d() mark done the task you ranked top in your last ranking or use short id, search() look if a task is present, pullexposed() pull but only consider tasks that have ranking data, edit() edit the text of a task, lookback() look at what tasks you have gotten done either that day or some number of days back.
I tend to do three rankings and then do the top task of the third ranking. I find that helps me and it identify what's actually high value without getting slogged by a huge list.
It also supports "users". Basically separate list. Like I have a Sunday list for all the fun stuff I want to do. Or if I have some majorly large task I'll spend 10 minutes dividing it down to the smallest tasks possible and then spin that off to its own user and work on that for half a day. That's rare, but if I have a single task that takes half a day it's nice. That means I can have stretch goals accumulate in the same list and then migrate them back out to the main list to follow up with some stretch goals against some of the other things I need to do.
Stick a GUI on that and maybe. It's all too complex. My .txt files work.
== To Do ==
Yes, ranking is important, as is keeping the details (thus collapse is handy). I made my own {{collapse language}} on Notepad++ that only does that.
Markdown changed my list.
Yeah it did.