I've been experimenting in my own branch to just refuse to change the start date if it would make it after the due date. But I'm finding that to be rather irritating.
One thing I've found is that if a due date is set on a parent task, the child task inherits that due date, and you cannot change the child task to be due later than the parent task. When you have the WorkView turned on, you can't see the parent task, and since you can't change the due date of the child task, it is very unclear what you have to do to move the due date later. And in the case of my branch where you can't change the start date either, the result is there is no way to push the task off the workview (aside from closing the task). I think the original suggestion of just having gtg move the due date if the start date gets shifted is in fact the right way to go. If gtg tries to be clever about limiting what the user can do (even such as graying out dates in the calendar), it may merely frustrate them and risk corner cases such as the one I described. -- Start Date should not be allowed to be after the End Date https://bugs.launchpad.net/bugs/532392 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: If a start date is set to be after a due date, the due date should be changed to reflect the start date. Currently, I have a task that starts in 11 days, but was due 15 days ago.. Yes.. I know, I am slacking with getting the task done. _______________________________________________ Mailing list: https://launchpad.net/~gtg Post to : [email protected] Unsubscribe : https://launchpad.net/~gtg More help : https://help.launchpad.net/ListHelp
