GothenburgBitFactory / taskwarrior

Taskwarrior - Command line Task Management
https://taskwarrior.org
MIT License
4.34k stars 292 forks source link

Wrong date in list report when traveling between timezones #2035

Open alex3kov opened 6 years ago

alex3kov commented 6 years ago

To report a bug...

$ env TZ='Europe/London' task list ID Age Due Description Urg 1 6w 2018-06-07 buy bilk 7.03

* Paste the output of the ```task diag``` command.

~: task diag

task 2.5.1 Platform: Linux

Compiler Version: 5.3.0 Caps: +stdc +stdc_hosted +LP64 +c8 +i32 +l64 +vp64 +time_t64 Compliance: C++11

Build Features Built: Mar 9 2016 20:12:54 CMake: 3.4.3 libuuid: libuuid + uuid_unparse_lower libgnutls: 3.4.10 Build type:

Configuration File: /home/username/.taskrc (found), 1583 bytes, mode 100644 Data: /media/localStorage/backup/Linux/taskwarrior_data (found), dir, mode 40750 Locking: Enabled GC: Enabled $EDITOR: vim Server: Trust: strict Certificate: , not readable, 0 bytes Key: , not readable, 0 bytes Ciphers: NORMAL Creds:

Hooks System: Enabled Location: /media/localStorage/backup/Linux/taskwarrior_data/hooks (-none-)

Tests $TERM: xterm-termite (277x66) Dups: Scanned 5 tasks for duplicate UUIDs: No duplicates found Broken ref: Scanned 5 tasks for broken references: No broken references found


2018-06-08 is a valid ISO8601 date, but TW always adds the time component. It sometimes messes up dates when traveling between timezones.
pbeckingham commented 6 years ago

This is not necessarily a bug. Needs more info regarding when the command above was run. It matters. There are times of day when the date is different in Moscow versus London.

alex3kov commented 6 years ago

@pbeckingham

Needs more info regarding when the command above was run.

I'm only entering the date in taskwarrior: task 1 modify scheduled:2018-06-08, without time, so I expect it to stay the same regardless of timezone. Taskwarrior adds the time component when no one asks it to (in json file).