gtg team mailing list archive

[Bryce Harrington <343058@xxxxxxxxxxxxxxxxxx>]

>From the comments it seems like sometimes when changing the due date
forward, one would want to have parent(s) be likewise extended, but not
always.  Sometimes you will want a notice that "the due date can't be
changed".

I'm not sure what the best solution here is.  But to brainstorm some (I
suppose obvious) options:

 A.  Silently refuse to change the due date of the child task

 B.  Silently change the due date of the parent task

 C. Show a confirmation dialog with text like, "Would you like to extend
the parent's due date as well?"  Obviously, this only solves the problem
for the case when changing from within a GUI, not via scripts or backend
syncing or whatnot.

 D. Add a 'hard deadline' property for due dates; when set this works
like A, when unset it works like B

 E. Refuse to change the due date of the child task, but add a red
flashing indicator or a statusbar message or something, so user knows
that the due date couldn't be changed.

I don't really like any of these options.  All of them except C is
likely to confuse *somebody*, and C seems excessively cluttery.

However, maybe for now C could be done, and if someone comes up with a
cleaner idea it can be replaced?

Anyone come up with any cleverer ideas?  Anyone know how other task
tools handle this situation?

-- 
Extend child due date will not work if parent due date is set earlier (feedback needed)
https://bugs.launchpad.net/bugs/343058
You received this bug notification because you are a member of Gtg
contributors, which is subscribed to Getting Things GNOME!.

Status in Getting Things GNOME!: Confirmed

Bug description:
Short : if you have a parent with a due date, the child due date cannot be set after the parent due date (on purpose, for logical reason.)

Problem is that it simply silently fail and it's not discoverable when using workview. People believe that this is a bug and don't understand. We need to give the user a feedback about why the due date cannot be set.



Original report:

Actions to reproduce:

1. Create a task. Set a due date.
2. Create a subtask. Observe the due date is the same as in #1.
3. Set the subtask date to some date *after* the date in #1.
4. Observe the subtask date is *still* the date from #1.

I don't know what the expected behaviour should be, but I was surprised by this, and I had to do some thinking before I realized what was happening.

I think if the user tries to extend the due date of a subtask past the due date of its parent, it is *possible* they also want to extend the parent's due date.

Some fixes would be:
 * Yes/No dialog saying "Would you like to extend the date of the parent task 'Parent Task Name' to YYYY/MM/DD?"
 * Automatically extend the date of the parent task if the subtask is the only subtask.