Hacker News new | ask | show | jobs
by natex 2968 days ago
Does anyone use Taskwarrior with more than just a few tasks? I have about 15 projects going at once and flip between them numerous times during the day. The projects might have several sub-projects and multiple next actions.

Are Projects/Subtasks implemented well?
5 comments
taborj 2968 days ago
I do. You can define the 'project', and then use that field in a variety of ways. I use the format 'Customer.Project', as I oftentimes have many projects with each customer. Using this method, I can sort by 'Customer' to get all projects for that customer, or I can get more granular and sort by 'Customer.Project'.

It's extremely versatile, and can be customized to suit your usage. I love it.

link
SEJeff 2968 days ago
Taskwarrior has the concept of a user defined attribute (UDA) which you can setup all kinds of fanciness for projects / filtering with. I use one called "prio" aka priority and generally set it to H|M|L. These allow you to customize taskwarrior to an insane degree. In fact, they actually rejected a contribution from me to add priority support natively when it could be done with a UDA:

https://taskwarrior.org/docs/udas.html

Really powerful software.

link
jecxjo 2967 days ago
I use to break all of my work up into smallest tasks possible. Was doing pomodoro, with two large projects, hardware and software, development and management, multiple feature and bug releases. So tons and tons of tasks! At one point I had it automated so when I was doing a bug fix I'd create a set of dependency connected tasks (Understand Bug, Create Fix, Create Unit Test, Code Review, Documentation, Push Update). I could easily have a hundred tasks in the queue at any given time.
link
kchr 2967 days ago
Wow, that was a great tip. I'm also finding myself splitting tasks into recurring steps like you mentioned, so automating this will save me lots of time.
link
brunoqc 2968 days ago
You can have projects with 'pro:name'. You can have sub projects with 'pro:name1.name2'. You can specify that a task depends on another one with 'depends:id1'.

I'm not sure how well it works with a lot of tasks. You might need to use filters a lot. tasksh review[1] might be useful too.

[1]: https://taskwarrior.org/docs/review.html

link
kchr 2967 days ago
$ task list pro:project_name
link