https://taskwarrior.org/Recent content on TaskwarriorHugo -- gohugo.ioen-usSat, 24 Dec 2022 00:00:00 +0000https://taskwarrior.org/news/news.20221224/Sat, 24 Dec 2022 00:00:00 +0000https://taskwarrior.org/news/news.20221224/FreeCinc Shutting Down FreeCinc has long hosted a Taskwarrior sync server (taskd). However, the service will be shutting down in February. The linked issue describes the reasons for this change. If you are a user of FreeCinc, please feel free to get in touch via GitHub discussions with any questions.https://taskwarrior.org/news/news.20211019/Tue, 19 Oct 2021 00:00:00 +0000https://taskwarrior.org/news/news.20211019/Taskwarrior 2.6.2 released Since Taskwarrior strives to be the very best, we are proud to announce the availability of the 2.6.2 bugfix release. Sometimes being best also means best at releasing versions with problems that need to be fixed 🙂 and (hopefully, eventually) catching them all. This bugfix-only release improves the upgrade path to 2.6.x, prevents corruption of the depends attribute when syncing, provides better support for detecting invalid write contexts and fixes a handful of small regressions introduced in our recent 2.https://taskwarrior.org/news/news.20211002/Sat, 02 Oct 2021 00:00:00 +0000https://taskwarrior.org/news/news.20211002/Taskwarrior 2.6.0 released Taskwarrior team is happy to announce the release of Taskwarrior 2.6.0, which brings a number of improvements to your favourite task management tool. To just pick a few - writeable and configurable contexts, support for XDG Base Directory Specification, and most importantly, the ability to use emojis in your task descriptions 🚀 We also made a number of stability and bug fixing improvements to multiple areas of TW, including parsing, display or platform compatibility.https://taskwarrior.org/news/news.20210103/Sun, 03 Jan 2021 00:00:00 +0000https://taskwarrior.org/news/news.20210103/Taskwarrior 2.5.3 Released The TaskWarrior team is happy to announce a new release! This bugfix-only release ships a critical fix for issue #2375, which can make your task report commands hang and eventually die in certain scenarios. There were no other critical issues reported specifically for the 2.5.2 release, which either means we did an exceptional job in backporting bugfixes from 2.6.0, or nobody tested the 2.5.2 release and we’re talking to ourselves here.https://taskwarrior.org/news/news.20191123/Sat, 23 Nov 2019 00:00:00 +0000https://taskwarrior.org/news/news.20191123/News: Timewarrior 1.2.0 released Timewarrior 1.2.0 is released! Here are the highlights: Print warning when a new tag is entered (#2) New command ‘undo’ (#9) New command ‘annotate’ (#68) Bash completion (#96) Show man pages with --help option The full changelog is an impressive read. Download here. This is a recommended upgrade for all Timewarrior users.https://taskwarrior.org/news/news.20180204/Sun, 04 Feb 2018 00:00:00 +0000https://taskwarrior.org/news/news.20180204/2018 Plans We have made good use of beer time at FOSDEM to lay out our plans for 2018. Here is what we are doing, starting immediately in most cases. Taskserver 1.2.0 Release The Taskserver 1.2.0 effort is overdue for release. The one issue that has been holding us back is a recurrence duplication bug, and we will be addressing that in a Taskwarrior release, not a Taskserver release. Taskwarrior 2.https://taskwarrior.org/news/news.20180203/Sat, 03 Feb 2018 00:00:00 +0000https://taskwarrior.org/news/news.20180203/Services Migration We are migrating services, and there will be a lot of changes. Here is a list of what is happening right now: We have a new support email address that should be used for all support requests: support@gothenburgbitfactory.org The old support email addresses will be forwarded while we work to change all references. Current source tarballs, and old releases will not be changed. The preferred mechanism to report a problem is to open a GitHub issue in the appropriate repository, for example: https://github.https://taskwarrior.org/news/news.20180203.2/Sat, 03 Feb 2018 00:00:00 +0000https://taskwarrior.org/news/news.20180203.2/Timewarrior 1.1.1 Released Timewarrior 1.1.1 is released. This is a bug fix release and we recommend that everyone upgrade to 1.1.1. There is one bug fix in this release, and it’s an important one that fixes a long-standing problem that has been there from the beginning. The problem is when a tracked interval spans an exclusion, the recorded interval has only one start and end time, and the exclusion is subtracted from this interval, resulting in multiple interval elements.https://taskwarrior.org/news/news.20180129/Mon, 29 Jan 2018 00:00:00 +0000https://taskwarrior.org/news/news.20180129/FOSDEM 2018: Taskwarrior Presence The Taskwarrior Team will be attending FOSDEM 2018 on February 3rd and 4th in Brussels. This is the second annual carbon-space meetup. What will the focus be this time? Are we traveling all this way and meeting up to give talks and demos? Will be sharing ideas and collaborating? Will we be planning features and releases? No. This time we’re all about the frites and beer. Wasn’t that the theme last time?https://taskwarrior.org/news/news.20180114/Sun, 14 Jan 2018 00:00:00 +0000https://taskwarrior.org/news/news.20180114/Activity Digest: May - December 2017 This is an ongoing series of activity reports, published monthly, to highlight activity in our projects. Here is what happened between May and December 2017. This is not a complete list of all activity, just work that results in a non-trivial change. For a full list, see the git history of all the projects. This covers a seven-month period. Due to unforeseen circumstances, there was a lengthy break in 2017.https://taskwarrior.org/news/news.20180113/Sat, 13 Jan 2018 00:00:00 +0000https://taskwarrior.org/news/news.20180113/Timewarrior 1.1.0 Released Timewarrior 1.1.0 is released. With 18 months of updates, many bugs fixed, and new convenience features added, Timewarrior 1.1.0 is stable and ready. Timewarrior tracks your time from the command line and generates reports. Your data is stored locally in clear text. It integrates well with Taskwarrior. Here are the changes in 1.1.0: Taskwarrior integration hook now uses a project Home.Garden as a single tag Home.Garden as well as individual Home, Garden tags Taskwarrior integration hook now stops the clock in more situations, such as deleting or waiting a task The tags command now supports filters New date names supported (see timew help date or man timew) Timewarrior and Taskwarrior now use the same date handling The continue command can resume tracking by @id When specifying a time without a date (e.https://taskwarrior.org/news/news.20170510_2/Wed, 10 May 2017 00:00:00 +0000https://taskwarrior.org/news/news.20170510_2/BYOP MeetUp in Gothenburg A BYOP (Bring Your Own Project) MeetUp was held in Gothenburg. We had the chance to present FLOD2 - our own CI, and distribute Taskwarrior stickers. The MeetUp presentation was followed by sitting together, hacking away and having a couple of beers.https://taskwarrior.org/news/news.20170510/Wed, 10 May 2017 00:00:00 +0000https://taskwarrior.org/news/news.20170510/Tasksh 1.2.0 Released Tasksh 1.2.0 is released. This is mostly a bug fix release, and is a recommended upgrade. The release is immediately available as a source tarball tasksh-1.2.0.tar.gz. Tasksh is a shell for Taskwarrior, providing a more immersive environment for list management. It has a review feature, shell command execution, and libreadline support.https://taskwarrior.org/news/news.20170509/Tue, 09 May 2017 00:00:00 +0000https://taskwarrior.org/news/news.20170509/Activity Digest: April 2017 This is an ongoing series of activity reports, published monthly, to highlight activity in our projects. Here is what happened in April 2017. This is not a complete list of all activity, just work that results in a non-trivial change. For a full list, see the git history of all the projects. Summary April was a relatively quiet month, but with two main efforts: Timewarrior 1.1.0 bug fixing, and deployment of our Flod CI system for all projects.https://taskwarrior.org/news/news.20170402/Sun, 02 Apr 2017 00:00:00 +0000https://taskwarrior.org/news/news.20170402/Code Repositories Moved The code repositories have been relocated to our new Gitea server. Gitea is a community managed fork of Gogs, lightweight code hosting solution written in Go and published under the MIT license. We like all of those things. You can browse all our repositories here: https://git.tasktools.org This means that there are several source-level packages which will temporarily have the old URL. They will catch up. If you are a developer with a repository clone, you’ll need to update the remote to the new URLs (task.https://taskwarrior.org/news/news.20170401/Sat, 01 Apr 2017 00:00:00 +0000https://taskwarrior.org/news/news.20170401/Activity Digest: March 2017 This is an ongoing series of activity reports, published monthly, to highlight activity in our projects. Here is what happened in March 2017. This is not a complete list of all activity, just work that results in a non-trivial change. For a full list, see the git history of all the projects. Summary Timewarrior bug fixes are bringing the 1.1.0 release closer. We are down to 7 open issues currently needing to be fixed.https://taskwarrior.org/news/news.20170308/Wed, 08 Mar 2017 00:00:00 +0000https://taskwarrior.org/news/news.20170308/HELLOTUX Shirts We’d like to thank HELLOTUX for doing a fantastic job designing embroidered apparel for Taskwarrior fans. This is the real thing - quality embroidery, not merely printed. Please check out the Taskwarrior section on the HELLOTUX website. There is currently a special offer, for a very limited time: HELLOTUX says: "… an offer for all the devs and fans of Taskwarrior: if you order 3 or more shirts or sweaters (one of them must be a Taskwarrior one) by this Friday (2017-03-10), we give a bonus Taskwarrior t-shirt for free.https://taskwarrior.org/news/news.20170301/Wed, 01 Mar 2017 00:00:00 +0000https://taskwarrior.org/news/news.20170301/Activity Digest: February 2017 This is an ongoing series of activity reports, published monthly, to highlight activity in our projects. Here is what happened in February 2017. This is not a complete list of all activity, just work that results in a non-trivial change. For a full list, see the git history of all the projects. Summary The team attended FOSDEM in Brussels, all meeting for the first time. No one was hurt.https://taskwarrior.org/news/news.20170209/Thu, 09 Feb 2017 00:00:00 +0000https://taskwarrior.org/news/news.20170209/Activity Digest: January 2017 This is an ongoing series of activity reports, published monthly, to highlight activity in our projects. Here is what happened in January 2017. This is not a complete list of all activity, just work that results in a non-trivial change. For a full list, see the git history of all the projects. Summary The rat parser is now mostly complete, and ready to take on the syntax of the rules system.https://taskwarrior.org/news/news.20170208/Wed, 08 Feb 2017 00:00:00 +0000https://taskwarrior.org/news/news.20170208/FOSDEM 2017: Reprise It was the first time the whole Taskwarrior Team met in carbon space. What do you get when people from the US, the Czech Republic, Germany, Sweden und Switzerland meet for the first time? A lot of fun! We had a great time-sharing thoughts and ideas, drinking beer and discussing various topics. There are some highlights to share: The rooms were really small, so we had to meet in the hotel lobby and talk to each other (what a pity…).https://taskwarrior.org/news/news.20170113/Fri, 13 Jan 2017 00:00:00 +0000https://taskwarrior.org/news/news.20170113/FOSDEM 2017: Taskwarrior Presence The Taskwarrior Team will be attending FOSDEM 2017 on February 4th and 5th in Brussels. There is no better opportunity to register your complaints directly and receive your own personalized sincere apology and refund. We should be easily recognizable: that far-away look in our eyes, logo stickers, beer and of course, no mouse. Find us, talk to us. We’d love to hear what you think.https://taskwarrior.org/news/news.20170102/Mon, 02 Jan 2017 00:00:00 +0000https://taskwarrior.org/news/news.20170102/Activity Digest: December 2016 This is an ongoing series of activity reports, published monthly, to highlight activity in our projects. Here is what happened in December 2016. This is not a complete list of all activity, just work that results in a non-trivial change. For a full list, see the git history of all the projects. Summary Both Taskwarrior and Taskserver improved GnuTLS support, in particular with more robust certificate validation, and error reporting/logging.https://taskwarrior.org/news/news.20161209/Fri, 09 Dec 2016 00:00:00 +0000https://taskwarrior.org/news/news.20161209/In-House Talk and Workshop at TNG Technology Consulting TNG Technology Consulting GmbH, of Unterföhring Germany, hosted an internal event “Techday” on December 9th, which is a regular occurrence at TNG. TNG invited Dirk Deimeke to attend and give a talk and workshop, where he discussed Taskwarrior and related projects, with a workshop that covered a lot of functionality. TNG covered attendance expenses, and also made a generous donation to the project.https://taskwarrior.org/news/news.20161203/Sat, 03 Dec 2016 00:00:00 +0000https://taskwarrior.org/news/news.20161203/Activity Digest: November 2016 This is an ongoing series of activity reports, published monthly, to highlight activity in our projects. Here is what happened in November 2016. This is not a complete list of all activity, just work that results in a non-trivial change. For a full list, see the git history of all the projects. Summary The focus has been on migrating code back to libshared.git, and in turn making use of that code.https://taskwarrior.org/news/news.20161116/Wed, 16 Nov 2016 00:00:00 +0000https://taskwarrior.org/news/news.20161116/Resolving with dnsimple Since a couple of weeks ago the resolving of our hostnames and domains is handled via services of dnsimple. They are kindly enough to sponsor the taskwarrior project. We will not only profit from the developer friendly management console but in particular from the powerful API to handle our DNS tasks when we move towards our new CI system flod2. Please check them out under dnsimple.com.https://taskwarrior.org/news/news.20161102/Wed, 02 Nov 2016 00:00:00 +0000https://taskwarrior.org/news/news.20161102/Activity Digest: October 2016 This is an ongoing series of activity reports, published monthly, to highlight activity in our projects. Here is what happened in October 2016. This is not a complete list of all activity, just work that results in a non-trivial change. For a full list, see the git history of all the projects. Summary Flod2 is now being rolled out for testing. This is a CI system rewrite that eliminates build server daemons and the pull model.https://taskwarrior.org/news/news.20161002/Sun, 02 Oct 2016 00:00:00 +0000https://taskwarrior.org/news/news.20161002/Activity Digest: September 2016 This is an ongoing series of activity reports, published monthly, to highlight activity in our projects. Here is what happened in September 2016. This is not a complete list of all activity, just work that results in a non-trivial change. For a full list, see the git history of all the projects. Summary Tasksh 1.1.0 released, Anomaly 1.1.0 released. Flod2 is a major update that greatly improves speed and reliability of the CI system.https://taskwarrior.org/news/news.20160905.2/Mon, 05 Sep 2016 00:00:00 +0000https://taskwarrior.org/news/news.20160905.2/Tasksh 1.1.0 Released Tasksh 1.1.0 is released, with an interactive review feature, ability to execute shell commands, and bug fixes. This release is a recommended upgrade. Here is a quick demo of the review feature: The release is immediately available as a source tarball tasksh-1.1.0.tar.gz. Tasksh is a shell for Taskwarrior, providing a more immersive environment for list management. It has a new review feature, shell command execution, and libreadline support.https://taskwarrior.org/news/news.20160905/Thu, 01 Sep 2016 00:00:00 +0000https://taskwarrior.org/news/news.20160905/Activity Digest: August 2016 This is an ongoing series of activity reports, published monthly, to highlight activity in our projects. Here is what happened in August 2016. This is not a complete list of all activity, just work that results in a non-trivial change. For a full list, see the git history of all the projects. Summary August saw a lot of documentation updates and preparation for the release of Timewarrior 1.https://taskwarrior.org/news/news.20160824/Wed, 24 Aug 2016 00:00:00 +0000https://taskwarrior.org/news/news.20160824/FrOSCon 2016 Materials Online Photo: Sujeevan Vijayakumaran Materials presented by Dirk Deimeke at FrOSCon 2016 are now online, as promised (click on Raw file): Introduction to Taskwarrior Taskwarrior and Taskserver Contributing to Taskwarrior Introduction to Timewarrior Taskwarrior Universe The materials are all updated with feedback from the events.https://taskwarrior.org/news/news.20160821/Sun, 21 Aug 2016 00:00:00 +0000https://taskwarrior.org/news/news.20160821/Timewarrior 1.0.0 Released Timewarrior 1.0.0 is released. Timewarrior tracks your time from the command line, and generates reports. Your data is stored locally in clear text. Integrates with Taskwarrior. Here are the features in 1.0.0: Start/stop time tracking Historical time tracking Taskwarrior integration Data correction commands Tagging of time blocks Automatic ‘fill’ of the available time Ability to define your work week, so that tracked time ‘wraps’ around your available time Vacations and holidays excluded from your work week Holiday data from https://holidata.https://taskwarrior.org/news/news.20160813/Sat, 13 Aug 2016 00:00:00 +0000https://taskwarrior.org/news/news.20160813/FrOSCon 2016 - Taskwarrior Coverage Taskwarrior will be well-represented at FrOSCon 2016, on August 20th and 21st, at the Bonn-Rhein-Sieg University of Applied Sciences. Dirk Deimeke will be presenting a series of related workshops and talks: August 20th Project Room C130 10:00 - 12:30 Workshop: Compile Taskwarrior and Taskserver 14:00 - 15:00 Talk: Introduction to Timewarrior 15:15 - 16:15 Talk: Taskwarrior Universe 16:30 - 17:30 Talk: Contribute to Taskwarrior (including FAQ, FOQ, Lessons learned)https://taskwarrior.org/news/news.20160810/Wed, 10 Aug 2016 00:00:00 +0000https://taskwarrior.org/news/news.20160810/Activity Digest: July 2016 This is an ongoing series of activity reports, published monthly, to highlight activity in our projects. Here is what happened in July 2016. This is not a complete list of all activity, just work that results in a non-trivial change. For a full list, see the git history of all the projects. Summary July was spent mostly getting Timewarrior ready for beta. Date 2016-07-02 - #18: The ‘total’ summands in the month report are not aligned with the column name fixed - #22: Warn when new tags are being created fixed - #28: Week number does not agree with Taskwarrior fixed - libshared: End of day is now 24:00:00 and not 23:59:59 - libshared: Week start is Monday, per isO-8601 2016-07-03 - #17: Task spanning over whole day should show up as taking 24:00 instead of 23:59 fixed - taskwarrior.https://taskwarrior.org/news/news.20160725/Mon, 25 Jul 2016 00:00:00 +0000https://taskwarrior.org/news/news.20160725/Timewarrior 1.0.0 Beta Release Timewarrior 1.0.0 is in beta! Please download and give us feedback. Download here: timew-1.0.0.tar.gz Online documentation here: Timewarrior Documentation Home Timewarrior is a companion to Taskwarrior, which tracks time, and then shows reports. It is intended to replace the timesheet command in Taskwarrior, and add much, much more. As a beta release, we hope you will download it and try it out. While Timewarrior has all its 1.https://taskwarrior.org/news/news.20160707/Thu, 07 Jul 2016 00:00:00 +0000https://taskwarrior.org/news/news.20160707/Activity Digest: June 2016 This is an ongoing series of activity reports, published monthly, to highlight activity in our projects. Here is what happened in June 2016. This is not a complete list of all activity, just work that results in a non-trivial change. For a full list, see the git history of all the projects. Summary The main focus for June is getting Timewarrior ready for an alpha, and subsequent beta release.https://taskwarrior.org/news/news.20160627/Mon, 27 Jun 2016 00:00:00 +0000https://taskwarrior.org/news/news.20160627/Clog 1.3.0 Released Clog 1.3.0 is released, with regular expression improvements, bug fixes, rule precedence and overlapping match support. This release is a recommended upgrade. The release is immediately available as a source tarball clog-1.3.0.tar.gz. Clog is a colorized log tail utility. It can spot patterns in an input stream and colorize or suppress the lines. It can also decorate the lines with time- or date-stamps. Clog has a full set of online documentation.https://taskwarrior.org/news/news.20160620/Mon, 20 Jun 2016 00:00:00 +0000https://taskwarrior.org/news/news.20160620/Timewarrior 0.9.5 Alpha Release Timewarrior 0.9.5 is in alpha! Please download and give us feedback. Download here: timew-1.0.0.tar.gz (Edit: Updated to the beta tarball) Online documentation here: Timewarrior Documentation Home Timewarrior is a companion to Taskwarrior, which tracks time, and then shows reports. It is intended to replace the timesheet command in Taskwarrior, and add much, much more. As an alpha release, we hope you will download it and try it out.https://taskwarrior.org/news/news.20160604/Sat, 04 Jun 2016 00:00:00 +0000https://taskwarrior.org/news/news.20160604/Activity Digest: May 2016 This is an ongoing series of activity reports, published monthly, to highlight activity in our projects. Here is what happened in May 2016. This is not a complete list of all activity, just work that results in a non-trivial change. For a full list, see the git history of all the projects. Summary The main focus for May is getting Timewarrior ready for an alpha release. The purpose of an alpha release is to gather feedback that guides the subsequent release.https://taskwarrior.org/news/news.20160522/Sun, 22 May 2016 00:00:00 +0000https://taskwarrior.org/news/news.20160522/Taskwarrior Tools Search The Taskwarrior Tools page now has interactive categorized search capabilities, thanks to a significant contribution by Bruno Vernay. We encourage you to take a look. This feature is driven by automated GitHub data extraction, which identifies taskwarrior-related projects and finds their metadata. Future enhancements will likely include other sources of projects. Before today, the tools list was manually curated, and a fraction of the size. It took many hours to update the list.https://taskwarrior.org/news/news.20160514/Sat, 14 May 2016 00:00:00 +0000https://taskwarrior.org/news/news.20160514/Timewarrior Preview Timewarrior is coming soon. Here is a peek at the work in progress.https://taskwarrior.org/news/news.20160501/Sun, 01 May 2016 00:00:00 +0000https://taskwarrior.org/news/news.20160501/Activity Digest: April 2016 This is an ongoing series of activity reports, published monthly, to highlight activity in the Taskwarrior project. Here is what happened in April 2016. This is not a complete list of all activity, just work that results in a non-trivial change. For a full list, see the git history of all the projects. Date 2016-04-01 - #1811: Support additional countable infinities reported - #1812: Urgency computations involving NaN are incorrect reported 2016-04-02 - #1813: taskrc(5) manpage: spurious “pri.https://taskwarrior.org/news/news.20160407/Thu, 07 Apr 2016 00:00:00 +0000https://taskwarrior.org/news/news.20160407/Taskwarrior running under “Bash on Ubuntu on Windows” Today we could verify that Taskwarrior works out of the box under “Bash on Ubuntu on Windows 10”. Either by installing it via apt-get (which pulls the regular Ubuntu package) or by compiling it. No changes needed to the source code. You compile it as you would do it on native Ubuntu. A few tests were failing. But no major ones. Enjoy the screenshot and enjoy the thoughts of being able to abandon Cygwin soon, if you are using Taskwarrior on Windows.https://taskwarrior.org/news/news.20160401/Fri, 01 Apr 2016 00:00:00 +0000https://taskwarrior.org/news/news.20160401/Activity Digest: March 2016 This is an ongoing series of activity reports, published monthly, to highlight activity in the Taskwarrior project. Here is what happened in March 2016. This is not a complete list of all activity, just work that results in a non-trivial change. For a full list, see the full Git history. Date 2016-03-01 - libshared: Gained JSON parser from Taskwarrior 2016-03-02 - Guides: New repo for Taskwarrior presentations online 2016-03-13 - Timewarrior: Design outline complete 2016-03-16 - libshared: Renamed from the older ‘common’ - a git submodule to share code across projects 2016-03-17 - Flod: Added support for submodules, using git clone --recursive .https://taskwarrior.org/news/news.20160301/Tue, 01 Mar 2016 00:00:00 +0000https://taskwarrior.org/news/news.20160301/Activity Digest: February 2016 This is an ongoing series of activity reports, published monthly, to highlight activity in the Taskwarrior project. Here is what happened in February 2016. This is not a complete list of all activity, just work that results in a non-trivial change. For a full list, see the full Git history. Date 2016-02-01 - #236: short help text fixed - task: Attribute modification delegated to type-specific objects - task: UDA definitions made more robust 2016-02-02 - #1721: Inconsistent failure mode on invalid task id fixed - #1734: Setting wait date on status:completed / status:deleted fixed - #1778: ‘' at end of description in ‘task edit’ merges task with following task fixed - #1787: Removing the due date of a task with no due date modifies the task fixed - task: Various attribute accessors were auto-vivifying, only to have the attribute removed later, which is silly 2016-02-03 - libshared: FS gained automatic BOM-removal logic - task: Assorted C++11-isms embraced - task: DOM Object demoted to functions 2016-02-05 - task: 2.https://taskwarrior.org/news/news.20160225/Thu, 25 Feb 2016 00:00:00 +0000https://taskwarrior.org/news/news.20160225/Taskwarrior for Android Released Author Konstantin Vorobyev has created an Android client with Syncing and many other features. Taskwarrior for Android has an embedded copy of Taskwarrior, and so inherits all the behaviors. Take a look at Taskwarrior for Android on Google Play. Taskwarrior for Android is open source, and can be found on bitbucket.org/kvorobyev/taskwarriorandroid. Congratulations Konstantin!https://taskwarrior.org/news/news.20160224/Wed, 24 Feb 2016 00:00:00 +0000https://taskwarrior.org/news/news.20160224/Taskwarrior 2.5.1 Released Taskwarrior 2.5.1 is released. Although this is a minor release, it contains many bug fixes and performance enhancements. There have been a lot of changes. Here are the new features: Nope There aren’t any, this is a bug fix and performance release. We just wanted to make it all work better. Don’t you just wish everyone did this once in a while? For full details, see the ChangeLog file included in the release.https://taskwarrior.org/news/news.20160209/Tue, 09 Feb 2016 00:00:00 +0000https://taskwarrior.org/news/news.20160209/Taskwarrior Workflow Study Taskwarrior aims to provide a toolkit of various capabilities, which can be cherry-picked to support many custom methodologies. We have learned over the years that everyone uses it differently, and for different things. There is a lot to be learned from how someone uses software, the features they use, and the ones they do not. So we are asking you to tell us how you use Taskwarrior, what for, which features, but more importantly why your choices make sense to you.https://taskwarrior.org/news/news.20160205/Fri, 05 Feb 2016 00:00:00 +0000https://taskwarrior.org/news/news.20160205/Taskwarrior 2.5.1 Beta Released This release is a bug-fix, code cleanup and performance release only. There are no new features, but the existing features all work a little more reliably, and a lot faster. For full details, see the ChangeLog file included in the release. The release is immediately available as a source tarball. This is a beta release, and is not recommended for stable environments.https://taskwarrior.org/news/news.20160201/Mon, 01 Feb 2016 00:00:00 +0000https://taskwarrior.org/news/news.20160201/Activity Digest: January 2016 This is an ongoing series of activity reports, published monthly, to highlight activity in the Taskwarrior project. Here is what happened in January 2016. This is not a complete list of all activity, just work that results in a non-trivial change. For a full list, see the full Git history. Date 2016-01-04 - clog: Code cleanup, inherited fixes and tests from task - taskd: The pki scripts now respect expiration date 2016-01-05 - flod: Began building on-demand system - taskwarrior.https://taskwarrior.org/news/news.20160101/Fri, 01 Jan 2016 00:00:00 +0000https://taskwarrior.org/news/news.20160101/Activity Digest: December 2015 This is an ongoing series of activity reports, published monthly, to highlight activity in the Taskwarrior project. Here is what happened in December 2015. This is not a complete list of all activity, just work that results in a non-trivial change. For a full list, see the full Git history. Date 2015-12-02 - timewarrior: Work began on sketching out a time-tracking solution, to integrate with task - details coming soon 2015-12-07 - taskwarrior.https://taskwarrior.org/news/news.20151201/Tue, 01 Dec 2015 00:00:00 +0000https://taskwarrior.org/news/news.20151201/Activity Digest: November 2015 This is an ongoing series of activity reports, published monthly, to highlight activity in the Taskwarrior project. Here is what happened in November 2015. This is not a complete list of all activity, just work that results in a non-trivial change. For a full list, see the full Git history. Date 2015-11-01 - Task: Migrated code from using C-style string formatting to C++11-style.https://taskwarrior.org/news/news.20151101/Sun, 01 Nov 2015 00:00:00 +0000https://taskwarrior.org/news/news.20151101/Activity Digest: October 2015 This is an ongoing series of activity reports, published monthly, to highlight activity in the Taskwarrior project. Here is what happened in October 2015. This is not a complete list of all activity, just work that results in a non-trivial change. For a full list, see the full Git history. Date 2015-10-07 - #1624: Dateformat wrongly interpreted fixed 2015-10-10 - #?https://taskwarrior.org/news/news.20151101.2/Sun, 01 Nov 2015 00:00:00 +0000https://taskwarrior.org/news/news.20151101.2/Cygwin Package Maintainer Needed We’re looking for someone to assume the responsibility of packaging Taskwarrior etc. for Cygwin. Cygwin doesn’t get the care and attention from us that it should. We often skip releasing on Cygwin because we don’t have the equipment and must borrow it, and furthermore don’t use Cygwin day to day, so every package update involves a full install, and it takes hours. The folks who do rely on and enjoy Cygwin deserve timely updates for every release.https://taskwarrior.org/news/news.20151029/Thu, 29 Oct 2015 00:00:00 +0000https://taskwarrior.org/news/news.20151029/Taskwarrior Mailing Lists The Taskwarrior user and developer mailing lists are back in play. Subscribe and talk to us: User Discussions: https://groups.google.com/forum/#!forum/taskwarrior-user. Developer Discussions: https://groups.google.com/forum/#!forum/taskwarrior-dev. The mailing lists are an additional communication channel, your original options remain: Email us at support@taskwarrior.org. User Q & A at answers.tasktools.org: Submit questions, receive answers, better answers get voted up. Requires account created at bug.tasktools.org. IRC #taskwarrior on freenode.net. Publicly logged on https://botbot.https://taskwarrior.org/news/news.20151021/Wed, 21 Oct 2015 00:00:00 +0000https://taskwarrior.org/news/news.20151021/Taskwarrior 2.5.0 Released After an intense five months which focused mainly on a more capable command-line parser, more extension-friendly behavior, and significant improvements to testing, Taskwarrior 2.5.0 is now released. This is a major release, with 1300+ code changes and well over a hundred bug fixes. We recommend all users upgrade, this release represents a significant increase in quality. There have been a lot of changes. Here are the highlights:https://taskwarrior.org/news/news.20151017/Sat, 17 Oct 2015 00:00:00 +0000https://taskwarrior.org/news/news.20151017/Taskwarrior 2.5.0 beta3 Released A new beta3 is available for the upcoming 2.5.0 release. The release is immediately available as a source tarball. This is a beta release, and is not recommended for stable environments.https://taskwarrior.org/news/news.20151012/Mon, 12 Oct 2015 00:00:00 +0000https://taskwarrior.org/news/news.20151012/Clog 1.2.1 Released Clog 1.2.1 is released, due to a problem with OSX and Xcode 7. The release is immediately available as a source tarball clog-1.2.1.tar.gz. Clog is a colorized log tail utility. It can spot patterns in an input stream and colorize or suppress the lines. It can also decorate the lines with time- or date-stamps.https://taskwarrior.org/news/news.20151001/Thu, 01 Oct 2015 00:00:00 +0000https://taskwarrior.org/news/news.20151001/Activity Digest: September 2015 This is an ongoing series of activity reports, published monthly, to highlight activity in the Taskwarrior project. Here is what happened in September 2015. This is not a complete list of all activity, just work that results in a non-trivial change. For a full list, see the full Git history. Date 2015-09-01 - Task: Added rc.rules.color.merge to control whether combined colors are merged (default) or overwritten.https://taskwarrior.org/news/news.20150929/Tue, 29 Sep 2015 00:00:00 +0000https://taskwarrior.org/news/news.20150929/answers.tasktools.org Online The answers.tasktools.org site is online, and providing not only the answer to your question, but those of many before you. It is becoming a valuable resource for both beginners and experienced users.https://taskwarrior.org/news/news.20150927/Sun, 27 Sep 2015 00:00:00 +0000https://taskwarrior.org/news/news.20150927/Clog 1.2.0 Released Clog 1.2.0 is released, with regular expression improvements and bug fixes. The release is immediately available as a source tarball clog-1.2.0.tar.gz. Clog is a colorized log tail utility. It can spot patterns in an input stream and colorize or suppress the lines. It can also decorate the lines with time- or date-stamps.https://taskwarrior.org/news/news.20150926/Sat, 26 Sep 2015 00:00:00 +0000https://taskwarrior.org/news/news.20150926/Vramsteg 1.1.0 Released Vramsteg 1.1.0 is released, with bug fixes and 64-bit value support. The release is immediately available as a source tarball vramsteg-1.1.0.tar.gz. Vramsteg, from the Swedish framsteg (progress), is a CLI progress bar that can be used from any script language. It supports color, labels, percentage completion, elapsed time and estimates.https://taskwarrior.org/news/news.20150916/Wed, 16 Sep 2015 00:00:00 +0000https://taskwarrior.org/news/news.20150916/Taskwarrior 2.5.0 beta2 Released A new beta2 is available for the upcoming 2.5.0 release. The release is immediately available as a source tarball. This is a beta release, and is not recommended for stable environments.https://taskwarrior.org/news/news.20150907/Mon, 07 Sep 2015 00:00:00 +0000https://taskwarrior.org/news/news.20150907/Taskwarrior 2.5.0 beta1 Released After an intense four-month effort, which focused mainly on a more capable command-line parser, more extension-friendly behavior, and significant improvements to testing, Taskwarrior 2.5.0 beta1 is now released. We are asking you to please build and test this release in your environment. This is a major release, with about 1100 code changes and a hundred or so bug fixes, but still resulting in a smaller codebase.https://taskwarrior.org/news/news.20150901/Tue, 01 Sep 2015 00:00:00 +0000https://taskwarrior.org/news/news.20150901/Activity Digest: August 2015 This is an ongoing series of activity reports, published monthly, to highlight activity in the Taskwarrior project. Here is what happened in August 2015. This is not a complete list of all activity, just work that results in a non-trivial change. For a full list, see the full Git history. Date 2015-08-01 - Task: Commands now have ‘DNA’, which determines how they behave, and allows more control than simply distinguishing between read-only and write commands.https://taskwarrior.org/news/news.20150801/Sat, 01 Aug 2015 00:00:00 +0000https://taskwarrior.org/news/news.20150801/Activity Digest: July 2015 This is an ongoing series of activity reports, published monthly, to highlight activity in the Taskwarrior project. Here is what happened in July 2015. This is not a complete list of all activity, just work that results in a non-trivial change. For a full list, see the full Git history. 2015-07-01 Task: C++ unit tests now produce the same colorful output in TTY mode as the Python tests.https://taskwarrior.org/news/news.20150701/Tue, 30 Jun 2015 00:00:00 +0000https://taskwarrior.org/news/news.20150701/Activity Digest: June 2015 This is an ongoing series of activity reports, published monthly, to highlight activity in the Taskwarrior project. Here is what happened in June 2015. Date 2015-06-02 Tasksh gains the ability to detect terminal width, and display colored banners. 2015-06-02 Tasksh gains UTF-8 support. 2015-06-02 Tasksh gains a more polished review command, which manages a GTD-like review session of your tasks, remembering where it left off, and not revisiting tasks too often.https://taskwarrior.org/news/news.20150627/Sat, 27 Jun 2015 00:00:00 +0000https://taskwarrior.org/news/news.20150627/GTD With Taskwarrior - a tutorial series Tom Sydney Kerckhove is writing a series of articles, explaining how he uses GTD with Taskwarrior. The first five articles are up: Part1 - Intro Part2 - Collection Part3 - Tickling Part4 - Processing Part5 - Doing The articles are well-written, and the material logically presented. We recommend you read them, and check for the latest articles. This post will be updated as more articles are published.https://taskwarrior.org/news/news.20150601/Mon, 01 Jun 2015 00:00:00 +0000https://taskwarrior.org/news/news.20150601/Activity Digest: May 2015 This is an ongoing series of activity reports, published monthly, to highlight activity in the Taskwarrior project. Here is what happened in May 2015. Date 2015-05-02 Taskwarrior and Taskserver learned how to lock files the POSIX way, instead of a platform-specific implementation. This should have happened years ago. Moving on… 2015-05-02 The ‘Taskwarrior’ name was standardized throughout the code.https://taskwarrior.org/news/news.20150524/Sun, 24 May 2015 00:00:00 +0000https://taskwarrior.org/news/news.20150524/Taskwarrior Live Demo Try Taskwarrior live in your browser.https://taskwarrior.org/news/news.20150511/Mon, 11 May 2015 00:00:00 +0000https://taskwarrior.org/news/news.20150511/Taskserver 1.1.0 Released After more than a year of improvements, Taskserver 1.1.0 is released. This is a major release, with greatly improved setup, security and logging, which make this a recommended upgrade. Changes include: Configuration New setup helper script, setup_server.bash, which interactively leads the whole setup and configuration process. When hosting, the configured server name is no longer ignored. Taskserver can now be restricted to IPv4 or IPv6. New man page for taskdctl.https://taskwarrior.org/news/news.20150510/Sun, 10 May 2015 00:00:00 +0000https://taskwarrior.org/news/news.20150510/Taskwarrior 2.4.4 Released Taskwarrior 2.4.4 is released. Although a minor release, there are significant bug fixes which make this a recommended upgrade. Changes include: Fixed a problem where the wrong task may be updated, if GC is disabled. This is the primary reason for the release. Fixed a problem where filters including parenthesized tags (... and (+DUE or +OVERDUE)) were incorrectly handled. 32-bit platform support. The obfuscate configuration setting will hide private data, intended for bug reporting.https://taskwarrior.org/news/news.20150509/Sat, 09 May 2015 00:00:00 +0000https://taskwarrior.org/news/news.20150509/Tasksh in Homebrew Tasksh, the Taskwarrior Shell, can now be installed using Homebrew on the Mac: $ brew install tasksh This means that all three related Taskwarrior family members can now be installed via Homebrew: $ brew install task ... $ brew install taskd ... $ brew install tasksh ... Existing Homebrew users can obtain the formulae: $ brew update ... Then later upgrade their Task software easily: $ brew upgrade .https://taskwarrior.org/news/news.20150430/Thu, 30 Apr 2015 00:00:00 +0000https://taskwarrior.org/news/news.20150430/Activity Digest: April 2015 This is an ongoing series of activity reports, published monthly, to highlight activity in the Taskwarrior project. Here is what happened in April 2015. Date 2015-04-01 The Hooks v2 API was implemented. While nothing changed with respect to the events or interfaces to the hooks scripts, there are now arguments passed to the hooks script. Whereas in the v1 Hooks API a hook script was effectively called like this: script <input >output The v2 API now effectively does this: script 'api:v2' 'args:task list' 'command:list' 'rc:~/.https://taskwarrior.org/news/news.20150419/Sun, 19 Apr 2015 00:00:00 +0000https://taskwarrior.org/news/news.20150419/Taskwarrior 2.4.3 Released User Defined Attributes (UDAs) have been enhanced so that type string attributes may now designate the sort order of allowed values. This enhancement permits the migration of the priority attribute to a UDA. This means you may now define your own priority levels, sorting and urgency coefficients. Although it may appear otherwise, there is no new monthly release cycle, it’s all a coincidence. The next release will likely take a little longer as we shift focus to Taskserver improvements.https://taskwarrior.org/news/news.20150504/Sat, 04 Apr 2015 00:00:00 +0000https://taskwarrior.org/news/news.20150504/Taskserver 1.1.0 beta1 Released Taskserver 1.1.0 is in beta, and we are asking you to please test this release in your environment. See https://taskwarrior.org/docs/taskserver/upgrade.html for instructions to upgrade your server. There have been a few changes: Configuration New setup helper script, setup_server.bash, which interactively leads the whole setup and configuration process. When hosting, the configured server name is no longer ignored. Taskserver can now be restricted to IPv4 or IPv6.https://taskwarrior.org/news/news.20150331/Tue, 31 Mar 2015 00:00:00 +0000https://taskwarrior.org/news/news.20150331/Activity Digest: March 2015 This is an ongoing series of activity reports, published monthly, to highlight activity in the Taskwarrior project. Here is what happened in March 2015. Date 2015-03-01 The Hooks Design page was moved out of the design section onto the main page. 2015-03-01 Scott pointed out that there is a performance drop since 2.3.0, which was fixed and further improved.https://taskwarrior.org/news/news.20150315/Sun, 15 Mar 2015 00:00:00 +0000https://taskwarrior.org/news/news.20150315/Taskwarrior 2.4.2 Released Taskwarrior 2.4.2 is released. This is primarily a bug fix release to address a bad hook problem that prevented on-modify hooks from modifying tasks. Additionally, the new context command is included, as are updated themes with higher contrast. Although this is a minor release, there are significant bug fixes and new features make this a recommended upgrade. Changes include: New context command. See the online documentation for full details.https://taskwarrior.org/news/news.20150301/Sun, 01 Mar 2015 00:00:00 +0000https://taskwarrior.org/news/news.20150301/Activity Digest: February 2015 This is the second of an ongoing series of activity reports, published monthly, to highlight activity in the Taskwarrior project. Here is what happened in February 2015. 2015-02-01 Renato adds a wrapper script that instruments all hooks scripts which gives the test framework an inspectable data structure that details hook script activity. 2015-02-03 It was reiterated that there is a place to check, to see what the latest release of Taskwarrior is: https://tasktools.https://taskwarrior.org/news/news.20150228/Sat, 28 Feb 2015 00:00:00 +0000https://taskwarrior.org/news/news.20150228/Taskwarrior 2.4.1 on Cygwin 32 and 64 bit Taskwarrior 2.4.1 is now available in binary and source package form for both Cygwin 32-bit and 64-bit systems. This release represents the first sync-capable Taskwarrior release on the Cygwin platform. This exposes our Cygwin users to new online services, such as: Inthe.AM - a free online task synchronization service, with client support, an iOS client, and a web interface. FreeCinc - a free online task synchronization service, for those who need to synchronize tasks across devices, but don’t wish to maintain their own Taskserver.https://taskwarrior.org/news/news.20150216/Mon, 16 Feb 2015 00:00:00 +0000https://taskwarrior.org/news/news.20150216/Taskwarrior 2.4.1 Released Taskwarrior 2.4.1 is released. Although this is a minor release, there are significant bug fixes and Hook support improvements that make this a recommended upgrade. Changes include: New German translation Hook scripts are now under much stricter control More feedback and help for Hook script authors The ‘date.iso’ setting allows you to enable (default) or disable support for ISO-8601 dates. This is because some of you have ‘dateformat’ settings that conflict The ‘recurrence’ setting enables (default) or disables recurring task instance generation Can now compile with musl(libc) Fixed assorted report definition problems Fixed assorted color theme problems Better color support in various places Lots of bug fixes For full details, see the ChangeLog file included in the release.https://taskwarrior.org/news/news.20150207/Sat, 07 Feb 2015 00:00:00 +0000https://taskwarrior.org/news/news.20150207/Activity Digest: January 2015 2015-02-07 This is the first of an ongoing series of activity reports, published monthly, to highlight activities in the Taskwarrior project. Here is what happened in January 2015. Date 2015-01-01 Taskwarrior 2.4.0 released. Including ISO date support, 2015-01-02 Some people are seeing unreadable color combination in 2.4.0 color themes. Some contrast and color improvements were made in the 2.https://taskwarrior.org/news/news.20150103/Sat, 03 Jan 2015 00:00:00 +0000https://taskwarrior.org/news/news.20150103/Date & Time Support Taskwarrior 2.4.0 supports many new date & time formatting options. These are all documented in the new Date & Time page. Here is a small sample: Read more about the extensive ISO-8601 support.https://taskwarrior.org/news/news.20150101/Thu, 01 Jan 2015 00:00:00 +0000https://taskwarrior.org/news/news.20150101/Taskwarrior 2.4.0 Released Taskwarrior 2.4.0 is released, it’s a major release, and a recommended upgrade. Happy new year. After almost a year of development, 108 bug fixes, 47 new/improved features, 1,750 code changes and over 50 community-provided patches, version 2.4.0 represents a significant improvement to task list management. Changes include: New localization: Portuguese and Esperanto translations New dateformat space handling New date support: ‘february’, extensive support for ISO-8601 New column formats: description.https://taskwarrior.org/news/news.20141221/Sun, 21 Dec 2014 00:00:00 +0000https://taskwarrior.org/news/news.20141221/Tasksh 1.0.0 Released The taskwarrior shell, tasksh 1.0.0, is released. Up to, and including, Taskwarrior 2.3.0, the shell command implemented this functionality. Starting with Taskwarrior 2.4.0, there is no shell command. Instead, there is the tasksh project. The tasksh supports libreadline, although it can be built without it. Libreadline provides command history and command editing. As a separate project, tasksh can innovate and release on its own schedule, as it remains independent of Taskwarrior, and supports all known releases.https://taskwarrior.org/news/news.20141111/Tue, 11 Nov 2014 00:00:00 +0000https://taskwarrior.org/news/news.20141111/Taskwarrior 2.4.0 beta3 A new beta 3 for Taskwarrior 2.4.0 is now available as a source tarball. Please note that this is beta software, and not suitable for everyday use. We welcome your feedback in the form of bug submissions, and general Questions & Answers.https://taskwarrior.org/news/news.20141025/Sat, 25 Oct 2014 00:00:00 +0000https://taskwarrior.org/news/news.20141025/Sort Column Indicator In the upcoming Taskwarrior 2.4.0, there is now the ability to apply a different color to the columns of a report that are part of the sort key. The report column headers are colored using the color.label setting, and the sort columns are colored by color.label.sort, if the setting exists. If it does not, color.label is used for all columns. The color themes are being updated, and some will take advantage of this new setting.https://taskwarrior.org/news/news.20141011/Sat, 11 Oct 2014 00:00:00 +0000https://taskwarrior.org/news/news.20141011/Taskwarrior 2.4.0 beta2 A new beta 2 for Taskwarrior 2.4.0 is now available as a source tarball. Please note that this is beta software, and not suitable for everyday use. We welcome your feedback in the form of bug submissions, and general Questions & Answers.https://taskwarrior.org/news/news.20140928/Sun, 28 Sep 2014 00:00:00 +0000https://taskwarrior.org/news/news.20140928/Cloud Server Reboots Rackspace has announced that it will reboot all of its cloud server infrastructure joining other hosting providers. The data center we are hosted in is the third in the row of IAD, DFW and ORD. The announced maintenance window is from 2014-09-28 1100 UTC to 2014-09-29 1101 UTC. This will cause interruptions here at taskwarrior.org. You can follow the status at status.tasktools.org and read more on global reboot at Rackspace’s status site.https://taskwarrior.org/news/news.20140915/Mon, 15 Sep 2014 00:00:00 +0000https://taskwarrior.org/news/news.20140915/Taskwarrior 2.4.0 beta1 Taskwarrior 2.4.0 is in beta, and available as a source tarball. Calc command task calc '1 + 1' Hint: it’s ‘2’, but it’s a beta, so who knows? And yes, it can do more than that. Enhanced DOM support task add due:123.due Date math task add ... due:eom wait:'due - 1week' Unicode: task add \\u2615 New command line parser. Why would you care? You wouldn’t. But we do, because it lets us be creative and add more useful features.https://taskwarrior.org/news/news.20140906/Sat, 06 Sep 2014 00:00:00 +0000https://taskwarrior.org/news/news.20140906/Fish Shell Completion Demo Taskwarrior 2.4.0 will be released with a fully updated Fish Shell completion script, from Roman Inflianskas. Here is a demo gif that Roman put together. The Fish shell has sophisticated completion capabilities, and this update takes full advantage of this.https://taskwarrior.org/news/news.20140816/Sat, 16 Aug 2014 00:00:00 +0000https://taskwarrior.org/news/news.20140816/Development Status Development is shifting focus for Taskwarrior and Taskserver. No more features will be added, and completeness, stability and testing become the new focus. The goal is to work towards good beta releases. There is no schedule for this work for a couple of reasons; we are more concerned with quality than delivery date, and as an all-volunteer organization, participation is not predictable (you can help). Although Taskwarrior 2.3.0, 2.https://taskwarrior.org/news/news.20140704/Fri, 04 Jul 2014 00:00:00 +0000https://taskwarrior.org/news/news.20140704/Taskwarrior 2.4.0 Preview The Taskwarrior 2.4.0 development branch has been unusable for a few weeks (mentioned here) while new functionality was integrated. It has been a long process, with about 750 code changes so far, but now all the tests are passing again. Does this mean it’s ready for alpha and beta? No, not yet, because now there is a need for a lot of new tests to cover all the new functionality.https://taskwarrior.org/news/news.20140607/Sat, 07 Jun 2014 00:00:00 +0000https://taskwarrior.org/news/news.20140607/Vit 1.2 in Homebrew The recently released Vit 1.2 is now available from Homebrew. Homebrew is “The missing package manager for OSX”, and includes recipes for several thousand packages. If you wish to install Vit easily on OSX, you simply update your brew recipes and install Vit like this: $ brew update ... $ brew install vit ... As any package manager should, this will resolve dependencies, which in this case include Taskwarrior itself and the Curses module.https://taskwarrior.org/news/news.20140524/Sat, 24 May 2014 00:00:00 +0000https://taskwarrior.org/news/news.20140524/Taskwarrior 2.4.0 Development Status Taskwarrior 2.4.0 is in development. The main feature of this release is a new command line parser, and some related features such as expression evaluation and ISO-8601 date support. This is a major undertaking, but the reward will be some very nice new features. Until now this work, on the 2.4.0 branch in the code repository has been carefully done so as to not completely break functionality.https://taskwarrior.org/news/news.20140510/Sat, 10 May 2014 00:00:00 +0000https://taskwarrior.org/news/news.20140510/Swiss Ubucon Taskwarrior Workshop On Saturday, May 10th 2014, Dirk Deimeke presented a Taskwarrior workshop at Swiss Ubucon. Dirk presented a live demo, with a handout PDF (which we will link here soon) that covers every aspect including downloading, building, installing, setup, first use, all the way to some of the more complex use cases. Take a look at Dirk’s logbook for details. Dirk also previewed the new command reference shown here:https://taskwarrior.org/news/news.20140429/Tue, 29 Apr 2014 00:00:00 +0000https://taskwarrior.org/news/news.20140429/Teaching the Parser New Tricks With Taskwarrior version 2.4.0, we are building a better command line parser. In addition to fixing a lot of annoying little bugs, we would like it to be more flexible and robust. That means it will be able to handle more strange inputs than before, but can it do better? We would like to see your most strange, supported or unsupported, twisted, Taskwarrior command line that you think should just work.https://taskwarrior.org/news/news.20140412/Sat, 12 Apr 2014 00:00:00 +0000https://taskwarrior.org/news/news.20140412/Taskserver Documentation Update The Taskserver setup documentation has been significantly improved. The setup page is: Setting up your own Taskserver The sub-pages now cover single topics: Pre-Installation Preparation Install binary package Install from tarball Install from git Server Configuration Server Start/Stop Add User to Server Configure Taskwarrior Syncing Taskwarrior Troubleshooting Feedback on the new pages would be appreciated.https://taskwarrior.org/news/news.20140407/Mon, 07 Apr 2014 00:00:00 +0000https://taskwarrior.org/news/news.20140407/Q & A Site Launched The new Q & A site is live! Take a look at the site, which can be found here: https://answers.tasktools.org There is a searchable knowledge base of community-provided questions and answers. The answers are voted and selected, good answers becomes more prominent, bad answers sink lower. You know how it works. As a brand-new site, the content is a little light right now, but as the questions come in, we believe this will grow into the primary resource for all those situations you need a little help with.https://taskwarrior.org/news/news.20140406/Sun, 06 Apr 2014 00:00:00 +0000https://taskwarrior.org/news/news.20140406/Vit 1.2 is released Version 1.2 of the VIT front-end for Taskwarrior is available for download now. Download here: vit-1.2.tar.gz. See the VIT 1.2 beta1 announcement for the features introduced in 1.2. The following are changes included since the beta release: the key can now be used in shortcuts exit with informative error if shortcut too long (see #42:) fix colors for running VIT in tmux do not print control characters to prompts fix recognition of backspace in tmux fix a prompt bug that prevented editing ‘vit -audit’ now creates a log with debug info Many thanks to Devendra Ghate and Nemo Inis, who provided quality feedback.https://taskwarrior.org/news/news.20140309/Sun, 09 Mar 2014 00:00:00 +0000https://taskwarrior.org/news/news.20140309/System Status Pages New system status pages are online, which provide up-to-the-minute status for the various services now online. The first is a Pingdom public report showing system status of the bug system, git hosting, web services and others. Check this page for outages. The second is an operations information page from StatusPage.io which shows status, uptime, response time and incidents. You’ll find links to the new status pages in the page footer on the front page.https://taskwarrior.org/news/news.20140303/Mon, 03 Mar 2014 00:00:00 +0000https://taskwarrior.org/news/news.20140303/Atlassian Licences We have received the very generous donation of software licences from Atlassian. This allows us to fully utilize Jira, Stash and Confluence Questions giving us high quality, integrated infrastructure, which in turn lets us focus on our goals of improving Taskwarrior and Taskserver. The Jira and Stash products are already in full use, with Confluence Questions coming online soon. Jira on bug.tasktools.org Stash on git.tasktools.org Thank you, Atlassian.https://taskwarrior.org/news/news.20140227/Thu, 27 Feb 2014 00:00:00 +0000https://taskwarrior.org/news/news.20140227/New Site Live We have shut off the old website, and replaced it with this. Although this site is a fraction of the size, it nevertheless has much less redundancy, and no obsolete documents. Take a look around, and hopefully you’ll find that there is a more logical structure, and clearer, updated documentation. It’s also a little sparse at the moment, but we are working on that. In addition to growing and completing the documentation set, there will be a replacement for the Q&A forums coming soon.https://taskwarrior.org/news/news.20140226/Wed, 26 Feb 2014 00:00:00 +0000https://taskwarrior.org/news/news.20140226/Registrations Disabled No new users on the Redmine site. We have shut off the registration of users on this site. This is part of our ongoing migration to new systems. This taskwarrior.org site content will be replaced soon, but the URLs will not change. All user accounts created prior to 2014-02-09 are already migrated over to the new issue tracking system. The newer accounts will be migrated shortly. To add bugs and feature requests please use: https://github.https://taskwarrior.org/news/news.20140220/Thu, 20 Feb 2014 00:00:00 +0000https://taskwarrior.org/news/news.20140220/VIT 1.2 beta1 is available Beta1 of the VIT front-end for Taskwarrior is available for download now. Download here: vit-1.2.beta1.tar.gz. VIT 1.2 brings a customizable way to interact with your tasks with user-defined shortcuts. You can now define keys to launch external commands with the currently selected task as input. Keybinds can now be specified in ~/.vitrc. For example, to use the external script tasknote when you press “ctrl + n”, you can do:https://taskwarrior.org/news/news.20140217/Mon, 17 Feb 2014 00:00:00 +0000https://taskwarrior.org/news/news.20140217/Server Migration As we migrate to our new servers, you’ll find that the services are being migrated first, and the content follows after. We are taking this opportunity to reorganize everything. This means there is a lot of missing content at the moment, please bear with us as we gradually move everything into place.https://taskwarrior.org/news/news.20140212/Wed, 12 Feb 2014 00:00:00 +0000https://taskwarrior.org/news/news.20140212/Git Hosting has migrated The new repository manager, Stash, is running on the new server: https://git.tasktools.org The old server will still be active for a little while longer, but will not be updated, so the repositories there are read-only and already out of date. You can re-clone your Taskwarrior repository from the new server, or update the origin URLs in your existing clone like this: $ cd task.git $ git config remote.https://taskwarrior.org/docs/task/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/task/Tasks The information here describes the task model exposed by TaskChampion. See the TaskChampion documentation for authoritative information. Tasks are stored internally as a key/value map with string keys and values. All fields are optional: the Create operation creates an empty task. Display layers should apply appropriate defaults where necessary. Atomicity The synchronization process does not support read-modify-write operations. For example, suppose tags are updated by reading a list of tags, adding a tag, and writing the result back.https://taskwarrior.org/docs/30second/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/30second/30-Second Tutorial Let’s get started. Here’s a quick demonstration showing how to perform basic task management. Here is an explanation of what is happening. First add two tasks. $ task add Read Taskwarrior documents later Created task 1. $ task add priority:H Pay bills Created task 2. Easy. Do you see that second one has a High priority? Now look at those tasks, using the report next. Notice that the two tasks are ordered by urgency, and the urgency is affected by the priority, among other things.https://taskwarrior.org/docs/3rd-party/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/3rd-party/3rd-Party Application Guidelines Taskwarrior can be extended by means of a third-party application, which can be a wrapper, or hook script. There are script examples of import and export add-ons that support many formats (clone the repository, look in taskwarrior.git/scripts/add-ons). Then there are more sophisticated applications such as Vit that provide a complete replacement UI. All of these provide interesting new features and improve ease of use for different kinds of users.https://taskwarrior.org/docs/commands/_get/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/commands/_get/_get The _get command is a DOM accessor. You can use this command to extract any piece of information stored by taskwarrior. For example to obtain the description of task 12: $ task _get 12.description Buy some milk You can specify multiple data items: $ task _get 12.description 12.project Buy some milk Kitchen You can use UUIDs: $ task _get a360fc44-315c-4366-b70c-ea7e7520b749.description Buy some milk The _get command makes it easy to map between ID and UUID:https://taskwarrior.org/docs/commands/_unique/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/commands/_unique/_unique The _unique command generates a filtered list of unique values for a given attribute. For example, to generate the list project names: $ task _unique project Home Home.Garden Work In addition to project, any attribute can be specified, for example, task status: $ task _unique status pending deleted completed There Filters You can specify a filter, to consider a subset of tasks, for example, here we see that the Home.https://taskwarrior.org/about/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/about/Göteborg Bit Factory is the organization that pays the bills, and supports all our Open Source projects.https://taskwarrior.org/docs/taskserver/user/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/taskserver/user/[4] Add User to Server A user account must be created, along with a key, cert and ID, before syncing may occur. Create Organization Before creating a user account, you may need to create an organization. An organization consists of a group of zero or more users. You can get away with just one organization, and in this example, we will create just one, named ‘Public’. You can create as many organizations as you wish (even one per user), and the purpose is simply to group users together.https://taskwarrior.org/docs/commands/add/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/commands/add/add The add command is the primary means of creating tasks. The simplest task requires only a description: $ task add Fix the leaky plumbing You can enter the description as above, just by including the words as command line arguments. You can also provide quoted strings: $ task add "Don't forget to shut off the main water valve first" In this example the double-quotes hide the single unclosed quote in “Don’t”.https://taskwarrior.org/docs/commands/append/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/commands/append/append The append command is a way to add words to the end of a task description: $ task add Fix plumbing $ task 1 append before the house floods While adding words to the end of the description, the append command can also update other attributes: $ task 1 append and before winter project:Home +repair $ task 1 list ID Age Project Tags Description Urg -- ---- ------- ------ ------------------------------------------------------ ---- 1 4min Home repair Fix plumbing before the house floods and before winter 1.https://taskwarrior.org/docs/best-practices/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/best-practices/Best Practices If you have installed Taskwarrior and gone through the intro and some of the tutorials, you may be wondering how to start using some features to help you organize your work. This is a simple tutorial, not intended to be complete, or methodology-specific, but just a start, to get you thinking about your task list, and how you might better rely on it. The default report (the report that runs when you just enter task) is thenext report.https://taskwarrior.org/docs/commands/burndown/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/commands/burndown/burndown.weekly (or .daily or .monthly) The burndown command shows a chart that depicts the number of pending, active and completed tasks over different time periods. This report makes it easy to gauge progress on a project, if a project is specified in the filter. With a filter, you can see the chart for any set of tasks. Alias There is an alias specified, by default, named burndown that expands to burndown.https://taskwarrior.org/docs/commands/calc/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/commands/calc/calc Taskwarrior has a calc command that exposes the algebraic expression evaluator used by all other commands and filters. This is handy for quick calculations from the command line, but combined with DOM access, can be very useful. Numbers This can be used to perform basic mathematics using the +, -, * and / operators: $ task calc 1+2*3 7 In the above example, care was taken to not allow that * operator to be expanded by the shell into a list of file in the current directory.https://taskwarrior.org/conduct/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/conduct/Taskwarrior Code of Conduct We are here to improve the software. There is no agenda. Be respectful of all contributors, all contributions, and everyone’s time, in all project-related forums. No exceptions. To report violations, please contact support@gothenburgbitfactory.org, and we will do the right thing.https://taskwarrior.org/docs/themes/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/themes/Color Themes Taskwarrior supports color themes. These are simply configuration files with defined color rules and rule precedence, which can be included in your .taskrc file like this: include /path/to/dark-blue-256.theme There are several themes included with the distribution, and the default .taskrc file you have references all of them, but these lines are commented out. Uncomment one line to use the theme. Overriding Colors You can override the color settings by placing changes after the include:https://taskwarrior.org/docs/commands/columns/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/commands/columns/columns The columns command shows a list of all the supported columns available for inclusion in a custom report. Each column may have multiple formats, and there are examples shown of each of those formats. As an example, a due date can be shown in various ways. It can be formatted according to the dateformat configuration setting. It can also be shown as a Julian date, a POSIX epoch, in ISO-8601 format, as an ‘age’ value or as a ‘countdown’ value.https://taskwarrior.org/docs/syntax/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/syntax/Command Line Syntax Taskwarrior has a flexible command line syntax, but it may not be clear at first what the underlying structure means. Here is the general form of the syntax: There are four parts to the syntax (filter, command, modifications, and miscellaneous), and each part is optional. Command Each time you run Taskwarrior, you are issuing a command either explicitly, or implicitly with the default command (the default.command configuration setting).https://taskwarrior.org/docs/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/configuration/Configuration Taskwarrior stores all configuration information in a file in your home directory, named .taskrc. The default .taskrc file contains a minimal set of entries, with only one required setting, which is: data.location=~/.task This is the only setting you need because Taskwarrior has sensible defaults for all the settings. This file is really just a list of settings for which you wish to override those defaults. Config Command The config command can be used to modify your .https://taskwarrior.org/docs/context/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/context/Context A context is associated with a location. An example of this might be that you perform tasks in three locations: At the office At home Study The tasks that pertain to your time in the office are meaningless if you are at home, and vice versa. This is just an example, and your contexts will likely be very different. If Taskwarrior allowed you to specify which context is currently active, then the tasks listed could be filtered accordingly You would then be working within a context.https://taskwarrior.org/docs/taskserver/control/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/taskserver/control/[3] Server Start/Stop You can now to launch the server: $ taskdctl start This command launched the server as a daemon process. This command requires the TASKDDATA variable. Your server is now running, and ready for syncing. Note that to stop the server, you use: $ taskdctl stop Check that your server is running by looking in the taskd.log file, or running this: $ ps -leaf | grep taskd Interactive or Non-Daemon Server A daemon server is typically how you would want to run Taskserver, but there may be times when you need to run the server attached to a terminal.https://taskwarrior.org/docs/commands/count/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/commands/count/count The count command simply counts tasks: $ task count 249 By default, all tasks are counted, which includes completed, deleted and pending. If you want to count just the pending tasks, add a filter: $ task status:pending count 32 If a context is active, the count command obeys it. See Also Other ways of counting tasks include: _unique commandhttps://taskwarrior.org/docs/dates/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/dates/Date & Time Taskwarrior supports date and time values. Date fields are used to track task creation, due date, scheduled date, end date and so on, as well as providing a date type for use with UDA fields. Whichever format is used to accept and display date and time, Taskwarrior resolves it to a UTC epoch value, accurate to one second. This is called Unix Time, POSIX time, or Epoch time.https://taskwarrior.org/docs/deprecated/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/deprecated/Deprecated Features Taskwarrior, Taskserver, Tasksh and Timewarrior have many features. With each release new features are added, and sometimes features are removed. A feature may be removed if it has been superseded by something better, is no longer relevant, or is very troublesome. With the Taskwarrior command line syntax becoming more formal and regular with every release, there will be a corresponding set of changes that remove ambiguous command line syntax, and add consistent syntax.https://taskwarrior.org/docs/dom/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/dom/DOM - Document Object Model Taskwarrior has a Document Object Model, or DOM, which defines a way to reference all the data managed by taskwarrior. You may be familiar with the DOM implemented by web browsers that let you access details on a page programmatically. For example: document.getElementById("myAnchor").href Taskwarrior allows the same kind of data access in a similar form, for example: 1.description This references the description text of task 1.https://taskwarrior.org/docs/commands/done/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/commands/done/done The done command is how tasks are marked as completed. $ task add Paint the door Created task 1. $ task 1 done Completed task 1 'Paint the door'. Completed 1 task. This sets the task status to completed, adds an end date and updates the modified date. En Passant There is a feature shared by several commands, named en passant, which allows further changes, above and beyond the command to be made.https://taskwarrior.org/docs/durations/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/durations/Durations Taskwarrior supports duration values. In the core, durations are used directly in one place - the recur attribute, used for recurring tasks. For example, here is a recurring task that recurs every monday: $ task add Take out the trash due:monday recur:weekly The value monday is interpreted as ‘next monday’, and the value weekly is interpreted as a 7-day duration. The other place where durations are supported directly is with UDA attributes of type duration.https://taskwarrior.org/docs/escapes/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/escapes/Escaping Command Line Characters Certain characters are interpreted by the shell. For example, the &. If you wish to include the & in a task description, you need to escape it, so the shell doesn’t interpret it. For example: $ task add Buy bread & milk This command is an error because of the &. The shell will consider this to be two commands: $ task add Buy bread & $ milk The shell treats the & character as an indicator that the command is complete and should be run in the background.https://taskwarrior.org/docs/commands/export/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/commands/export/export The export command accepts a filter, and generates a JSON formatted text output. For example: $ task 1 export {"id":1,"description":"Buy milk","entry":"20141018T050231Z","modified":"20141018T050231Z","status":"pending","uuid":"a360fc44-315c-4366-b70c-ea7e7520b749","urgency":"2"} This command allows you to extract all data from Taskwarrior, in a machine-readable, standard format. The export command is used by many Taskwarrior extensions to gain access to the data. JSON Format The JSON is formatted according to the Taskwarrior JSON Format, which consists of one JSON object per line, where one object represents one task.https://taskwarrior.org/support/faq/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/support/faq/FAQ - highlights from years of Q&A. Have a question that's not here? Ask us… Taskwarrior Q: How do I implement Pomodoro? Taskwarrior currently doesn't support the pomodoro technique, not because it doesn't have all the necessary features, but because it has no way to notify the user if a given point in time has arrived. Remember: most of the time, Taskwarrior isn't running. You can however use the pomodoro timer or any other timer software (KTeaTimer, Gnome's Tea Timer, Gnome's pomodoro shell extension, pyStopWatch, or any of the many timers out there), together with taskwarrior to manage and prioritize your ToDo list.https://taskwarrior.org/docs/filter/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/filter/Filters A filter is a set of command line arguments that specify a set of tasks and filters can range from being simple to very complex. The simplest filter is an empty filter, and we can illustrate this with the count. $ task count 100 These 100 tasks are the tasks, pending and completed, which represent are all the tasks known to Taskwarrior. Any command that accepts a filter also accepts no filter, as shown above.https://taskwarrior.org/docs/help/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/help/Getting Help There are several forms of help available All support avenues are listed at the Support page. https://taskwarrior.org If you find you have any questions, you can get answers in several ways. The website has user forums, issue tracking and online documentation, including this tutorial. There is also a Command reference PDF that we recommend you download and use. It shows all the supported commands and options at a glance.https://taskwarrior.org/docs/hooks_guide/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/hooks_guide/Hook Author’s Guide This guide walks through the process of writing and testing a Taskwarrior hook script. While this is a simple and straightforward process for developers, there are still many considerations. A hooks script will be developed, and the various concerns discussed. Example Hook Script As an example, we’re going to create a hook script that detects tasks that refer to Taskwarrior bug numbers (ie ‘TW-179’) in the description, and replaces the bug number with a URL that links to the bug.https://taskwarrior.org/docs/hooks/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/hooks/Hooks v1 The API defined here is the [Hooks v1] API. Later versions will allow a script to determine which version of the Hooks API is being used. Hooks A hook system is a way to run other programs/scripts at certain points in Taskwarrior’s execution, so that processing can be influenced. These callout points correspond to locations in the code where some critical processing is occurring. These are called events.https://taskwarrior.org/docs/hooks2/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/hooks2/Hooks v2 The API defined here is the [Hooks v2] API. This API is part of the TaskWarrior 2.4.3 release. Events No change. Input No change. Output No change. Exit Status No change. Interfaces No change. Command Line Arguments To support an evolving Hooks API, Taskwarrior must provide hook scripts with a mechanism for determining which version of the Hooks API is providing the context for the script. It is anticipated that in future versions, new events will be added, and changes to the interfaces will occur.https://taskwarrior.org/docs/recurrence/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/recurrence/How Recurrence Works A recurring task is a task with a due date that keeps coming back as a reminder. Here is an example: task add Pay the rent due:1st recur:monthly until:2015-03-31 Created task 123. This task has a due date, a monthly recurrence, and an optional until date coinciding with the end of the lease. A recurring task is given a status of recurring which hides it from view, although you can see it in the all report.https://taskwarrior.org/docs/build/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/build/How To Build Taskwarrior This is for developers. Specifically those who know how to use tools, satisfy dependencies, and want to set up a development environment. It is not user-friendly. You’ll need these tools: git cmake make C++ compiler, currently gcc 4.7+ or clang 3.3+ for full C++11 support Python 2.7 or later (for tests) Bash (for tests) You’ll need these libraries: GnuTLS libuuid (unless on Darwin/BSD) Specifically the development versions, uuid-dev on Debian, for example.https://taskwarrior.org/docs/bugs/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/bugs/How to Report a Bug Please report bugs and odd behavior when you see it. We don’t necessarily know it’s broken, unless you tell us. A good bug description improves response time and reduces the burden on the developers. It helps if you first determine whether this is a known bug. To do this, you will need to look at the current list of bugs here: https://github.com/GothenburgBitFactory/taskwarrior/issues If you don’t see the bug listed, sign up for an account at the link above, and create a new issue.https://taskwarrior.org/docs/features/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/features/How to Request a Feature We encourage you to request features. You can submit a feature request using our issue tracking system. Simply create an account, create an issue, and set the type to either ‘improvement’ or ‘feature’, at your discretion. But there is a little more to it than that. After all, wouldn’t you like to see your request implemented? What Makes a Good Feature Request? Requesting a feature is easy, but you must remember that it doesn’t mean it will get done.https://taskwarrior.org/docs/ids/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/ids/ID Numbers Taskwarrior assigns ID numbers to tasks. The ID number is actually a simple line count of the entries in the pending.data file. When a task is completed or deleted, it is moved to the completed.data file, and loses the ID. All tasks, pending or otherwise, have a UUID, and are always addressable by UUID. By keeping the tasks in two separate files, average performance is improved. This works because most of the commands and reports are based on only the pending tasks, which are in the pending.https://taskwarrior.org/docs/commands/info/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/commands/info/info The info command (the full command name is information) is a way to display all the task metadata in human-readable form. This includes UDAs. $ task 1 info Name Value ------------- ------------------------------------------------------------------ ID 241 Description Need to map stored duration values to the supported subset on load Status Pending Project tw.240 Entered 2014-09-19 11:32:22 (2 weeks) Last modified 2014-09-19 11:32:22 (2 weeks) Tags bug Virtual tags PENDING READY TAGGED UNBLOCKED UUID 91bbb01f-4a43-42bd-a7a3-03ce3a2451ff Urgency 4.https://taskwarrior.org/docs/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/introduction/Introduction Hello, and welcome to Taskwarrior. This is the first of many tutorials, and covers first-time use. First Time Use As a first-time user, you are going to need a configuration file and a data directory. Taskwarrior will create both of these for you, in your home directory, the first time you run Taskwarrior. Here is an example: $ task version A configuration file could not be found in ~ Would you like a sample /home/alice/.https://taskwarrior.org/docs/jobs/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/jobs/Job Openings With a family of Open Source projects, there is always work to be done. We need help, in all kinds of areas, for all skill levels. This is Open Source volunteer work. The pay is zero, but you’ll get your hands dirty in a set of active projects that need all different kinds of help. Perhaps you’re a professional with a little time here and there to donate to the projects.https://taskwarrior.org/docs/license/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/license/The MIT License (MIT) Copyright 2006 - 2017, Paul Beckingham, Federico Hernandez. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:https://taskwarrior.org/docs/commands/list/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/commands/list/list The list report is a customizable report, which means that many aspects of the report is configurable. You may override any of these aspects by modifying the Taskwarrior configuration. The definition of the list report can be shown using the show command like this: $ task show report.list Config Variable Value ----------------------- -------------------------------------------------------------- report.list.columns id,start.age,entry.age,depends.indicator,priority,project, tags,recur.indicator,scheduled.countdown,due,until.age, description.count,urgency report.list.description Most details of tasks report.list.filter status:pending report.list.labels ID,Active,Age,D,P,Project,Tags,R,Sch,Due,Until,Description,Urg report.list.sort start-,due+,project+/,urgency- These are five settings that define the report.https://taskwarrior.org/docs/commands/log/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/commands/log/log The log command is the same as the add command, with one difference - the task is added in the completed state. Sometimes it is necessary to record tasks that are already completed, if you are faithfully tracking work. For example: $ task log Order the materials +home +construction This task is immediately recorded as completed, which means it will not be displayed on any report that shows pending tasks.https://taskwarrior.org/docs/commands/missing/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/commands/missing/Missing Documentation You found a broken link in the documentation. There are many of these because the documentation is a work in progress, so you don’t get a prize. Please bear with us as the pages are slowly being written, by unpaid volunteers, in poor working conditions, against their better judgment, uphill, in the rain.https://taskwarrior.org/docs/commands/modify/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/commands/modify/modify The modify command is the most direct way to change a task, for example, replacing a description: $ task 1 modify This is the new description Here a tag is added, and another removed from a task: $ task 1 modify -home +garden The same change, but to several tasks: $ task 1 3 5-10 modify -home +garden The same change, but to a set of tasks matching the filter:https://taskwarrior.org/docs/named_dates/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/named_dates/Named Dates The term ‘date’ is used here to describe a timestamp of varying precision and specificity. The terms ‘timestamp’, or ‘datetime’ also apply. Taskwarrior supports the notion of specifying dates in several ways. There are ISO-8601 dates: 2014-06-07T16:55:04-05:00 2014-W23 20140607 There are rc.dateformat dates, the default being Y-M-D: 2014-06-07 This document enumerates and defines other dates, such as tomorrow and many others. Days of the Week The days of the week are interpreted as the next day in the future.https://taskwarrior.org/docs/philosophy/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/philosophy/Taskwarrior Philosophy Taskwarrior is developed using a philosophy that explains a lot about why certain decisions have been made, and will continue to be made. All Taskwarrior family projects follow this same philosophy. Openness The source code, plans, designs, bugs, testing, docs, and website are all free and open source. Your data is kept as plain text, and never held hostage by a proprietary format. You are welcome to contribute and identify improvements in all aspects of the project.https://taskwarrior.org/docs/commands/prepend/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/commands/prepend/prepend The prepend command is a way to add words to the beginning of a task description, and it mirrors the append command: $ task add sandwich $ task 1 prepend make me a While adding words to the beginning of the description, the prepend command can also update other attributes: $ task 1 prepend sudo project:Food $ task 1 list ID Age Project Description Urg -- ---- ------- ----------------------- ---- 1 4min Food sudo make me a sandwich 1.https://taskwarrior.org/docs/priority/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/priority/Priority Taskwarrior has supported the notion of task priority since the beginning. Priority was defined to have four allowable values, H, M and L, with the additional option of having no priority at all. The values represent High, Medium, Low and No priority. The L value is considered a higher priority than no priority. Priority has been used to sort tasks in most built-in reports. Beginning with Taskwarrior 2.4.3, priority is no longer a core attribute, and is replaced with an equivalent User Defined Attribute.https://taskwarrior.org/docs/history/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/history/Release History This is a summary of the Taskwarrior ChangeLog file. It is no longer updated. Release Date Description 2021-10-03 2.6.0 will overhaul recurrence and add more flavors of recurring tasks. 2021-01-03 2.5.3 is a bug fix, code cleanup, performance release only - no features. 2020-12-05 2.5.2 is a bug fix, code cleanup, performance release only - no features. 2016-02-24 2.https://taskwarrior.org/docs/report/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/report/Reports Taskwarrior has three kinds of reports. There are built-in reports that cannot be modified, such as info and summary. There are built-in reports which can be redefined completely or eliminated, such as list, next. And finally there are your own custom reports. To generate a list of all the reports, use the reports command: $ task reports Report Description active Active tasks all All tasks blocked Blocked tasks blocking Blocking tasks burndown.https://taskwarrior.org/docs/searching/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/searching/Searching Searching for keywords and patterns in tasks is straightforward, and uses the /pattern/ syntax. First we create some sample tasks, then we’ll search them. $ task add foo $ task add bar $ task add baz In order to locate that first task, by the keyword foo we do this: $ task /foo/ list ID Age D Description Urg -- ----- - ----------- ---- 1 1min foo 0 The / characters delimit the search term, indicating what Taskwarrior should do.https://taskwarrior.org/support/authors/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/support/authors/The Taskwarrior team would like to thank the following for their contributions to this site: Adam Coddington Andrey Utkin Brian Exelbierd Bruno Vernay Cory Donnelly Daniel Doubrovkine Daniel Shahaf David J Patrick David Derek Schrock Dirk Deimeke Evropi Federico Hernandez Heikki Hokkanen Jack Desert Jens Erat Jeremiah Marks Jeremy John Reeder Johannes Schlatow John Florian Killian Widdis Klaus Ethgen Lars Wallenborn Loren Rogers Louis-Claude Canon Maarten Joosten Manuel Koell Markus Beppler Matthias Radig Owen Clarke Paul Beckingham Peter Rochen Renato Alves Rick Cogley Roman Inflianskas Scott Kostyshak Simon Berger Slaven Banovic Stefan Frühwirth Sébastien Le Corre Toger Tom Sydney Kerckhove Tomas Babej Vladislav Bykov Wade Duvall Wilhelm Schuermann Will Dietz Will Paul Wim Schuermann b4ernd berceanu catern darless jamur2 jrabbit kushaldas lerouge tvincent philipw modem_down Micheal Meier Florian Preinstorfer Matt Kraai Jens K.https://taskwarrior.org/docs/commands/synchronize/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/commands/synchronize/synchronize The synchronize command, which first appeared in version 2.3.0, connects your Taskwarrior client to a Taskserver instance, uploads local changes, downloads remote changes, and merges the results. You can have several clients making local changes all of which sync to a single server instance, and they will all be kept up to date. The Taskserver is designed to handle multiple clients that may not have synchronized recently, all with local changes, with only temporary network connectivity, and still do the right thing.https://taskwarrior.org/docs/tags/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/tags/Tags & Virtual Tags The basic tag syntax is very powerful and simple to use. There are two ways to use this, shown here: $ task +HOME list $ task -WORK list These two commands illustrate the complete tag interface. The first command is a filter that lists only tasks that have the HOME tag. The second command is a filter that lists only tasks that do not have the WORK tag.https://taskwarrior.org/docs/taskserver/ciphers/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/taskserver/ciphers/Cipher Selection By default, Taskserver 1.0.0 uses the GnuTLS cipher set: PERFORMANCE:%SERVER_PRECEDENCE Taskserver 1.1.0 and later uses this GnuTLS cipher set: NORMAL Taskwarrior uses: NORMAL You may wish to override these ciphers with a set that satisfies your security needs. A vigilant Taskserver administrator may wish to respond to news of various cipher weaknesses. For example, a more secure set would be to use only TLS 1.2 and these ciphers:https://taskwarrior.org/docs/taskserver/configure/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/taskserver/configure/[3] Server Configuration Configuring the server is straightforward, but needs a little planning. Choose a Data Location A location for the data must be chosen and created. The TASKDDATA environment variable will be used to indicate that location to all the taskd commands. $ export TASKDDATA=/var/taskd $ mkdir -p $TASKDDATA If the TASKDDATA variable is not set, then most taskd commands require the --data ... argument, otherwise the commands rely on the TASKDDATA value to indicate the location.https://taskwarrior.org/docs/taskserver/git/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/taskserver/git/[2.3] Installation Installing Taskserver from git is a matter of cloning the git repository and building the server. Dependencies Before building the software, you will need to satisfy the dependencies by installing the following: git GnuTLS (likely libgnutls-dev, ideally version 3.2 or newer) libuuid CMake (2.8 or newer) make A C++ Compiler (GCC 4.7 or Clang 3.0 or newer) Note that some OSes (Darwin, FreeBSD, …) include libuuid functionality in libc.https://taskwarrior.org/docs/taskserver/package/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/taskserver/package/[2.1] Installation Installing Taskserver from a binary package is the simplest option, but you will need to refer to your package manager’s documentation and procedures for doing this. Take a look at the Download page for examples. Generally there are too many package managers to make a complete list with instructions here. Most importantly, for now, Taskserver is a new product, and there are very few packages available. It is expected that this situation will change soon.https://taskwarrior.org/docs/taskserver/tarball/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/taskserver/tarball/[2.2] Installation Installing Taskserver from a tarball is a matter of downloading the tarball, extracting it, satisfying dependencies and building the server. Dependencies Before building the software, you will need to satisfy the dependencies by installing the following: GnuTLS (likely libgnutls-dev, ideally version 3.2 or newer) libuuid CMake (2.8 or newer) make A C++ Compiler (GCC 4.7 or Clang 3.0 or newer) Note that some OSes (Darwin, FreeBSD, …) include libuuid functionality in libc.https://taskwarrior.org/docs/taskserver/prep/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/taskserver/prep/[1] Preparation Installing and operating a server is not a casual task. You need to prepare. Backup Your Data Let’s reinforce a good habit and make a backup copy of your data first. Here is a very easy way to back up your data: $ cd ~/.task $ tar czf task-backup-$(date +'%Y%m%d').tar.gz * Now move that file somewhere safe. All software contains bugs, so make regular backups. Choose a Machine A suitable machine to run your Taskserver is one that is always available.https://taskwarrior.org/docs/taskserver/protocol/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/taskserver/protocol/Protocol Selection Taskserver 1.1.0 ordinarily binds to the first interface that matches the hostname and port, regardless of whether that is an IPv4 or IPv6 interface. You have several options to control this. The server can be configured to bind to the hostname and port in several ways: $ taskd config server localhost:53589 $ taskd config server 127.0.0.1:53589 $ taskd config server ::1:53589 The first is the most typical way to set up the server, and is protocol agnostic, in that localhost is usually defined for all interfaces.https://taskwarrior.org/docs/history_td/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/history_td/Release History This is a summary of the Taskserver ChangeLog file. Release Date Description 2015-05-10 1.1.0 Featuring: Improved security (certificate and hostname verification, optional CRL).Improved logging (more diagnostics, more details, log to STDOUT, JSON validation, statistics restored).Improved portability (Solaris, musl libc).Improved documentation (man tskdctl, online docs).Improved quality (test framework improved, client testing implemented).Improved setup (automated setup, taskd.service script).Improved PKI scripts (CN, no SAN).IPv4/IPv6 support.https://taskwarrior.org/docs/taskserver/setup/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/taskserver/setup/https://taskwarrior.org/docs/taskserver/sync/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/taskserver/sync/[5] Syncing Taskwarrior You are now ready to sync your Taskwarrior client. You will do this differently depending on whether this is the first sync per device, or one of the many subsequent syncs. First Time Sync The first time you sync is special - the client sends all your pending tasks to the server. This is something you should only do once. Run this: $ task sync init Please confirm that you wish to upload all your pending tasks to the Task Server (yes/no) yes Syncing with host.https://taskwarrior.org/docs/taskserver/why/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/taskserver/why/Why Do I Need a Taskserver? You may not need a Taskserver. You may be content with using Taskwarrior on a single device. But if you wish to share tasks between several clients, the Taskserver is the only option that properly syncs data. With a Taskserver, you can share tasks between clients/devices, eliminating the need to keep your data up to date on multiple clients, reducing data entry. One nice side effect of using a Taskserver is an automatic backup of your tasks.https://taskwarrior.org/docs/taskserver/taskwarrior/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/taskserver/taskwarrior/[4] Configure Taskwarrior If you have configured Taskserver and created a user account (or better yet, someone created an account for you) then you now have details needed in the configuration of your Taskwarrior client. You should have these files and this information: CA ca.cert.pem Client certificate: first_last.cert.pem Client key: first_last.key.pem User key (yours will be different): cf31f287-ee9e-43a8-843e-e8bbd5de4294 Organization: Public Account name: First Last Server:port host.domain:53589. In the server configuration we used localhost as an example.https://taskwarrior.org/docs/review/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/review/Tasksh Review Beginning with release 1.1.0 the Taskwarrior shell (tasksh) has a review command that lets you review your tasks. Reviewing your task list is important because you need to make sure you work on the more urgent tasks first, and also make sure your list is up-to-date. Only with accurate metadata (due dates, priorities, …) will your task list reflect real world needs. Periodic review will help you maintain the right due dates, priorities, dependencies, tags, project assignments and so on, while removing tasks that are no longer needed.https://taskwarrior.org/docs/terminology/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/terminology/Terminology Taskwarrior and Taskserver use a lot of terminology that is not obvious. Those terms are defined here. active When a task is started, like this: $ task 1 start It gains a start attribute, which is a date. When started, a task is considered active, until completed, deleted or stopped. alias An alias is name that can be used on the command line, which is replaced by its definition at run time.https://taskwarrior.org/docs/triage/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/triage/Triage This is the initial assessment of an issue. The purpose is to get it moving in the right direction and make sure it gets noticed in the right context, which means making sure that every issue has a suitable category and version. New issues are reported all the time, sometimes the submitter fills in fields, sometimes not. That cannot be controlled. Everything else can. Initial Assessment Move the issue to the correct project.https://taskwarrior.org/docs/taskserver/troubleshooting-sync/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/taskserver/troubleshooting-sync/Troubleshooting Sync Here is a list of problems you may encounter, with the most common ones listed first. The single most common problem has been that the Taskserver Setup Instructions were not properly followed. Please review the steps you took. It is always a good idea to make sure that you are using the latest release of Taskwarrior and Taskserver, not just because bugs are fixed that may help you, but also because the solutions below are geared toward the current releases.https://taskwarrior.org/docs/unicode/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/unicode/Unicode All text in Taskwarrior is UTF8, which means any Unicode characters can be entered and stored. Here is a demo: $ task add Download U+266C U+2669 for the plane Created task 5. $ task 5 list ID Age P Description Urg 6 10s M Download ♬ ♩ for the plane 3.9 Both the U+NNNN and \uNNNN specifiers are supported, but it is usually simpler to use the first, which does not require the backslashes to be escaped in shells and scripts.https://taskwarrior.org/docs/taskserver/upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/taskserver/upgrade/Upgrading Taskserver Upgrading to Taskserver 1.1.0 requires some configuration changes. The required changes are mostly concerned with improvements to security and encryption. Updating the software itself is straightforward. Upgrade the Software This is simply a matter of shutting down the server, installing the new software, modifying the configuration as discussed below, and restarting the server. Before doing this, please read the issues below, so that you will be prepared, and more secure.https://taskwarrior.org/docs/urgency/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/urgency/Urgency Taskwarrior has a next report, which is sorted by decreasing urgency. If that measure of urgency represents or approximates your idea of what is important, then the tasks you should start next will appear near the top of that list. But what is urgency? Sometimes a task list is driven by dependency, due date or perhaps priority. In these situations it is relatively easy to select a task to work on next.https://taskwarrior.org/docs/examples/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/examples/Usage Examples Here are some Taskwarrior command line examples that cover a variety of topics. While this is not a reference for the features and command line, perhaps you will learn something new… Some of the examples are deliberately chosen because there is more than one solution, in which case all are presented, for comparison. 30 Second Tutorial $ task add Read Taskwarrior documents later $ task add priority:H Pay bills $ task next $ task 2 done $ task $ task 1 delete Creating Tasks Creating tasks is straightforward, but here are some tips:https://taskwarrior.org/docs/udas/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/udas/User Defined Attributes (UDA) Taskwarrior supports a set of standard attributes for a task, known as the core attributes. These include project, description, due and so on. There are more than 20 standard attributes (see columns for a full list). They are necessary to provide all the functionality of Taskwarrior. For example, the project attribute is used to provide feedback on completion of a project, the projects command itself, and project hierarchy filtering.https://taskwarrior.org/docs/using_dates/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/using_dates/Using Dates Effectively A task does not require a due date, and can simply be a statement of need: $ task add Send Alice a birthday card However, this is exactly the kind of task can benefit from having a due date, and perhaps several other dates also. There are several dates that can decorate a task, each with its own meaning and effects. You can choose to use some, all or none of these, but like all Taskwarrior features, they are there in case your needs require it, but you do not pay a performance or friction penalty by not using them.https://taskwarrior.org/docs/verbosity/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/verbosity/Verbosity Taskwarrior provides feedback when commands are run, the amount of which can be controlled. There is a configuration variable named verbose that can be set to different values to control verbosity. By default, the value is: verbose=yes This value causes Taskwarrior to show all feedback. Conversely, it can be set to: verbose=no This restricts the amount of feedback, but still retains useful information. To remove all feedback, use the setting:https://taskwarrior.org/docs/advice/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/advice/What Have We Learned From This Open Source Project? Here is the collected wisdom that we have gained from running the Taskwarrior project for more than a decade. It has been rewarding, enjoyable, and sometimes frustrating. We learned a lot about users and Open Source expectations. Advice To Open Source Project Contributors Start an open source project if you want to learn all you can about software design, development, planning, testing, documenting, and delivery, enjoy technical challenges, administrative challenges, compromise, and will be satisfied hoping that someone out there is benefiting from your work.https://taskwarrior.org/docs/start/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/start/What is Taskwarrior? Taskwarrior manages your TODO list from your command line. It is flexible, fast, efficient, unobtrusive, does its job then gets out of your way. Taskwarrior scales to fit your workflow. Use it as a simple app that captures tasks, shows you the list, and removes tasks from that list. Leverage its capabilities though, and it becomes a sophisticated data query tool that can help you stay organized, and get through your work.https://taskwarrior.org/download/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/download/Download source tarball or access code repository here. Download Latest stable release taskwarrior 2.6.2 (Released 2022-03-16): task-2.6.2.tar.gz SHA3 92e547ac6bb88659e674877a19cb88dc9687be2ab989f0279b04f286 Changelog taskd server 1.1.0 (Released 2015-05-10): taskd-1.1.0.tar.gz SHA1 ded339deeee65277e4712f71a9159502f8b20b52 Changelog Command reference taskwarrior 2.5.3: task-2.5.3.ref.pdf See supported platforms for operating systems. Quick Setup Build the task program according to the directions in the INSTALL file. This transcript illustrates a typical installation: $ ls task-2.6.2.tar.gz $ tar xzvf task-2.6.2.tar.gz $ cd task-2.6.2 $ cmake -DCMAKE_BUILD_TYPE=release .https://taskwarrior.org/docs/workflow/Mon, 01 Jan 0001 00:00:00 +0000https://taskwarrior.org/docs/workflow/Workflow Examples Everyone uses Taskwarrior differently. Here are some example workflows, to make you think about your own particular approach. Joshua Where do you use Taskwarrior? Everywhere to get track of things. I keep my personal thing separated and two zones for work projects each on its own git repository. For what kind of work do you use Taskwarrior? At work to organize my projects, chop them into small tasks, have a log of what I am doing, and a log of how did I solve problems.