gtg-contributors team mailing list archive

[Izidor Matušov <izidor.matusov@xxxxxxxxx>]

Take a look at how it works now in GTG:
  1, Open a task editor
  2, Set start date into far future (e.g. 2012-04-29)
  3, Set due date into not so far future (e.g. 2012-04-22)
  4, Watch the result in task browser or re-open the task editor

The current result: *due date* is updated to 29th, not start date.

I suggested to move *start date* to 22nd.

We need to have a consistent policy across the whole GTG. Greying out 
doesn't work for text widget and calendar in a task editor.

Use cases:
  1, I set start date and it is after due date => start > due
  2, I set due date and it is before start date => due < start
  3, Parents have shorter due date => parent.due < child.due
  4, Children have longer due date => children.due > parent.due

Don't forget that by changing anything by use case 3 or 4, you may 
trigger 1 and 2 in any parents/children.

I propose:
  1, change start date to be due date, I find star date not so 
important as due date
  2, same as 1
  3, "Disable" changing due date by setting it to parent.due
  4, Decrease all children's due dates to the new due date: because 
when your boss tells you to finish project a week earlier, you would 
need to change just one date and subtasks shrinks to that date.

What do you think? How would you solve those use cases?

Izidor