Consistency between start and due dates
Suppose I have a task whose due date is already set. What is the expected behavior of the application if I try to set the start date after the due date? I see at least two possible events that may trigger this:
1) I accidentally select the wrong start date
2) I want to postpone the task and decide to define the new start date first
I find the current behavior somehow inconsistent. In 0.2.4 shipped with Precise, I am apparently allowed to set start date > due date, GTG does not complain. In the trunk version (rev.1179) I can still do that from the dropdown menu, but changing dates in the task window would behave differently: if start date > due date, due date is set to start date.
Before filing a bug report, please let me know what is GTG supposed to do in this case. For instance, the Thunderbird Lightning plugin would simply not allow start date > due date.
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- GTG Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- Roquentin
- Solved:
- Last query:
- Last reply: