GothenburgBitFactory / GothenburgBitFactory/taskwarrior

[TW-232] More informative recurrance messages

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

Description

_Aikido Guy on 2011-03-24T14:14:48Z says:_

> task add "Pay bills" project:Blah due:yesterday recur:2weeks

> Created task 50.

I expect a new task that has a due date of yesterday (March 23rd) and another task that will occur 2 weeks after yesterday's task (April 6th). After some fiddling, I can determine that yesterday's task is 51 and the task in 2 weeks is task 52. Neither of them have ID's that are the same as task reported to me (i.e. 50). For me, I would prefer that I did not need to perform this "fiddling". When I created the task above, it would have been nice if task informed me what it was doing right away so that I am aware of what is happening "behind the scenes".

Something like:

> task add "Pay bills" project:Blah due:yesterday recur:2weeks

> Created task 50 as the main task for accounting purposes.
> Spawned task 51 from 50 since that is the first task for you to complete.
> Spawned task 52 from 50 since it also occurs within the recurrence period.

I don't care about the future tasks popping up into my task list automatically. I am just concerned that it is difficult to track what task has done this first time that I have added a recurring task. Especially for a new user like me, I get confused easily and such a set of messages would help me to understand more clearly.

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.