GothenburgBitFactory / GothenburgBitFactory/taskwarrior

Initial task parameters are being included in task log of info

Open
#3,767 3 comments 0 reactions 0 assignees View on GitHub
topic:per-task-ops type:enhancement
Dominant language
C++
Stars
6.1k
Forks
423
Avg merge
1d 19h
Merged PRs (30d)
11

Description

With the release of taskwarrior 3.3, we got back the task log feature, **awesome**, thanks for that! However, I noticed that the log now includes the initial values of task parameters. This is different from how it was previously (which in of itself doesn't have to be a bad thing) and I think it also doesn't really make sense: after all the point of the log is to show _changes_. One can easily infer the initial values by inspecting the changes and comparing them to the current value. Moreover, this log can take up a lot of screen estate if you have large amount of UDAs (which is usually the case for tasks imported via `bugwarrior`).

Hence, would it be possible to go back to showing _only changes to the task in the task info log_? Is there a technical reason for this new behavior? I know that taskwarrior moved to sqlite in the 3.x version, so perhaps that has something to do with this new behavior.

If it is technically feasible, I could also have a go at implementing this "fix" myself if @djmitche is stretched for time. I haven't had a look at the new `task info` implementation, but I am somewhat familiar with the previous version of the code-base.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.