Start Date should not be allowed to be after the End Date
Bug #532392 reported by
Chris Johnston
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GTG |
Fix Released
|
Medium
|
Volodymyr |
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.
Related branches
lp:~exufer/gtg/bugfix
- Bryce Harrington (community): Approve
-
Diff: 36 lines (+10/-0)3 files modifiedAUTHORS (+1/-0)
CHANGELOG (+3/-0)
GTG/taskeditor/editor.py (+6/-0)
Changed in gtg: | |
importance: | Undecided → Medium |
tags: | added: love |
Changed in gtg: | |
milestone: | none → 0.3 |
status: | New → Triaged |
Changed in gtg: | |
status: | Triaged → Confirmed |
tags: | added: toreview |
Changed in gtg: | |
milestone: | 0.3 → 0.2.9 |
Changed in gtg: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
What should be the default behaviour ?
1) We refuse to set a start date after a due date. Logical but not good for user experience.
2) We extend the due date. Fine. But what if the due date is modified afterward ? We refuse it ? Or we always obey to "the last order" ?
This is, AFAIK, not as simple as previously thought.