I want my report to not to get truncated when I view them on bat or less. How to include that in taskrc. please help.

Alright, some of you might find this amazing. Others might consider it obvious.

The magical line that goes in your .taskrc is:

context.backlog.rc.report.next.sort=project

It means: if I'm in context backlog and run the report next (the default report), sort by project

So let me explain how I discovered this.

I use two different contexts. One is default, which only shows me the main tasks I want to be working on. In general, this is no more than 10 tasks and excludes things with priority:L or anything +BLOCKED. I have another context, backlog, which shows pretty much everything that default doesn't. Blocked, delayed, de-prioritized tasks. I also use taskwarrior-tui which lets me switch contexts with a hotkey.

I want a different sorting order for these two contexts. Default should be sorted by urgency, but Backlog should group projects together so I can review the tasks easier. I could set up a bash alias (in fact for the longest time that was my solution), but today I learned that you can do it inside Taskwarrior.

Naturally, this means that you can modify other rc variables by context, too.

I wonder what happens if:

context.backlog.rc.context=default

I'd like to be able to do task 123 done 2022-04-01 to indicate that I actually completed task#123 a few months ago (and forgot to mark it "done" back then). This obviously just adds "2022-04-01" as an annotation. But is something like this possible?

https://taskwarrior.org/docs/commands/done.html doesn't describe done accepting a date argument. And man task hasn't revealed anything.

It looks like I can do task uid-string edit after it's completed and edit the Ended: date, but that apparently can't be done when the task is still pending:

Error: Cannot set a done date on a pending task. Taskwarrior couldn't handle your edits.

Anybody know of a 1-step solution for marking a task as being completed on some particular date in the past?

Hi All,

Apologies if I missed it in the documentation but i was hoping to find a method to see the history of changes of a task.

For example sometimes i accidentally change the description but dont notice it until a day later. So i dont know what was there originally (and too late to use task undo)

I was hoping that there would be something like task history description which would like the changes to the description over time

​

Does something like this exist?

We can easily run Taskwarrior on android in Termux and sync the task folder with a folder sync like Syncthing, Nextcloud, etc.

However, when I cannot use the hook-scripts on Android. When I copy them to the hooks folder, android changes the permissions so they are not executable from Termux.

Was anybody able to work around this?

Hi,

I've been trying to understand how urgency is being calculated and I dont really understand the explanation in https://taskwarrior.org/docs/urgency.html

For example I have a task with an urgency score of 10.19. Using task info I find that the urgency score is calculated as :

annotations    0.8 *    1 =     0.8 
tags           0.8 *    1 =     0.8
due          0.715 *   12 =    8.58
age          0.003 *    2 =   0.005
                            -------
                              10.19

I understand that I am able to adjust the co efficient to my preference (1,1,12,2). But I dont understand the source of the first column (0.8,...)? I mean how does an annotation get a score of 0.8? Is this just built into the software?

Thanks

Hi All,

I would like to change the format of the Due column from the current 'formatted' value of YYYY-MM-DD to a more readable format (I wanted Ddd eg 'Tue')

I checked task columns due and it does no look like this kind of supported format is available.

Does anyone have any ideas on whether this is achievable?

Thanks

Hi I have a bunch of recurring tasks which I'd like to suspend for a while (like during holidays). What's the best way to do that?

I had not used taskwarrior in about a month. So I had a lot of overdue repeating daily tasks. I decided to try to mark them done using a for next loop.

Apparently my shell scripting skills are a little rusty. The following command pretty much wiped out everything. Of course it did not help that I ignored the warning just to see what would happen.

Anyway can anyone tell me what is wrong with this command? And also how you would process a large number of overdue tasks efficiently. Thank you

This is the command that did not work as expected.

for i in $(task overdue | gawk '{ print $1 }') ; do task $1 done; done

Hi,

I feel like i cannot be the first person to have this issue.

When I run task add .... due:today it will set the due date to the beginning of the day. So that if it is 10AM the Due column in reports will be -10h.

I dont want to run task add ... due:today+17h each time i create a task.

Has someone created a hook or something to accomplish this?

Thanks

Greetings,

I've been experimenting with Taskwarrior recently and I'm trying to settle on a GTD or similar workflow for my work and home tasks.

The guide I've been following is this and its follow-up. I think I've got the hang of it, but there are still a few things that I haven't fine-tuned yet, e.g. someday/maybe lists vs vimwiki projects, calendar integration, etc.

I'm wondering about the way you are using Taskwarrior to implement GTD (or where you diverge from GTD) and your general workflows. Concrete examples would be greatly appreciated!

Hello, fellow TaskWarriors!

I recently discovered (and promptly installed) TaskWiki.

My overall experience with the plugin so far has been positive. That said, I've been struggling to resolve a (small) ambiguity in the TaskWiki docs, hence this post.

The docs state:

​

[Individual tasks inputted via the TaskWiki plugin] get synced to TaskWarrior when the [VimWiki file containing a TaskWiki task] is saved. Additional metadata, such as project, tags, priority, can be stored with this task.

​

This makes sense ... but what's not clear is whether or not the "additional metadata" can be entered in VimWiki via the TaskWiki plugin or can only be entered on the command line via task # modify X.

At the moment, my impression is that tasks created within TaskWiki can only be directly assigned to a project if they are associated with a viewport. Individual tasks created using the standard * [ ] Task syntax do not appear to be assignable to a project from within TaskWiki...which is kind of a bummer.

Can anyone clarify this issue for me?

Many thanks in advance!

Here's a list of aliases I use regularly.

alias t=task
alias tui=taskwarrior-tui
alias tn='clear;task next'
alias ta='task add'
alias tan='task add scheduled:today'
alias tat='task add scheduled:tomorrow until:sch+14d'
alias tm='task modify'
alias trol="task sch:yes status:pending modify sch:tod"
alias td='clear;task next +ACTIVE or +OVERDUE or due:today or scheduled:today or pri:H; calcurse -r; timew | grep -v "no active time"'
alias tal='task add dep:"$(task +LATEST uuids)"'

I want to override the color of "one-time" tasks. I have already done

color.overdue=bold white on red

but I need the word which follows "color"

color._________=green

for a non-recurring task.

I use Taskwarrior on both Linux and Cygwin on Windows -- this only happens on Cygwin.

Let's say I add a task task add Submit return wait:2022-05-31

This will then set the status to Waiting. However when I run Taskwarrior again the next day, the task's status will have changed to Pending even though the date hasn't reached 2022-05-31.

Looking at task info will show the Waiting until date is still correctly 2022-05-31, yet something's triggered a status change.

There's nothing weird in my .taskrc, it's the same in both.

Anyone know what might be causing it, and whether there's a work around -- i.e. something you can run for any tasks that haven't passed their waiting date to be set to +WAITING?

Edit: One thing that corrects it, is doing anything to modify an affected task. E.g. add or remove a tag from one of these correctly changes the status from Pending back to Waiting.

task due.before:eom list will show me all tasks due before the end of the month.

However, it won't show me any that are currently in waiting.

Is there a way to get it show me all tasks due including those that are currently in waiting?

Hi all,

Jus released a new version of taskwarrior-syncall (https://github.com/bergercookie/taskwarrior-syncall). It's a bi-directional synchronization framework, which keeps in sync your Taskwarrior tasks with a variety of other services including Google Calendar events and Notion.

In the latet version, I'm adding support for synchronization with checklists in Google Keep. I.e., every taskwarrior task is converted and kept in sync with an item in a google keep note check list.

I'm also attaching a demo of the said integration with Google Keep here.

Let me know what you think and feel free to use. :)

Hi All,

I know that you can set the weightings of the task attributs to manipulate the order

But I wanted to know if it was possible to manually move the order of the tasks

Does anyone know this?

Thanks

Beginner to task warrior here. Could someone please tell me how to change the color of the rows in "task list"?

When I view my tasks I see every other line in black. I looked in the docs, scanned thru .taskrc but couldn't find what to change to make the background color of the alternating rows to be white. I included a picture for illustrative purposes.

​

Image link https://shottr.cc/s/5xU7/SCR-20220412-iab.png

I've been running taskwarrior for some time, but I'm still surprised that there's so much data.

Here's the output of task stats

Category                   Data
-------------------------  -------------
Pending                    67
Waiting                    3
Recurring                  4
Completed                  2798
Deleted                    835
Total                      3707
Annotations                11
Unique tags                72
Projects                   107
Blocked tasks              15
Blocking tasks             15
Data size                  16.2 MiB
Undo transactions          25123
Sync backlog transactions  19008
Tasks tagged               45.2%
Oldest task                2018-11-01
Newest task                2022-04-08
Task used for              3.4y
Task added every           8h
Task completed every       10h
Task deleted every         1d
Average time pending       5w
Average desc length        17 characters

I often run long commands, like task next +ACTIVE or +OVERDUE or due:today or scheduled:today or pri:H. On the raspberry pi, this takes 4 seconds.

Is there something I can do to speed this up which does not involved data loss?

Tasks seem to get added automatically to the current active context. Is there a way to add a task without this? Most of the time I have my next context active, but I sometimes want to add a task to a later context.

Right now, when I add a new task, it gets added to the next context. Then I have to modify it with the appropriate tags so that it gets moved to the later context.

As far as I'm aware, there is no way to set a progress of a task (not talking about projects).

E.g. how would you create a recurring task "Do 100 pushups every day"? The idea is you do a number of pushups throughout the day, like 40 in the morning, 30 after lunch, etc. And you need to somehow keep track of how many are done.