Urgency wrong for task with closed sub-tasks
Bug #1258451 reported by
Tim Waugh
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GTG |
Fix Released
|
Low
|
Unassigned |
Bug Description
The calculated "urgent" due date for a task, i.e. the quantity used for sorting the "Due" column, is wrong for a task with closed sub-tasks.
Take these tasks:
* Task1 due:2013-12-17
\
'--Subtask1 due:2013-12-05 closed:2013-12-01
* Task2 due:2013-12-07
When the task browser shows these tasks, sorted as "Due ^", Task1 is shown at the top (with due description "in 11 days") before Task2 (with due description "tomorrow").
This is because get_urgent_date() for Task1 is returning 2013-12-05, even though that task has already been closed.
I suggest ignoring closed sub-tasks for calculating the urgent date for a task and its sub-tasks.
Related branches
lp:~shikhachowdhary28/gtg/Bug1258451
Rejected
for merging
into
lp:~gtg/gtg/old-trunk
- Gtg developers: Pending requested
-
Diff: 12 lines (+2/-0)1 file modifiedGTG/core/task.py (+2/-0)
tags: | added: love |
Changed in gtg: | |
assignee: | nobody → Shikha Chowdhary (shikhachowdhary28) |
Changed in gtg: | |
status: | New → In Progress |
Changed in gtg: | |
status: | Fix Committed → In Progress |
milestone: | none → 0.3.2 |
importance: | Undecided → Low |
Changed in gtg: | |
assignee: | Shikha Chowdhary (shikhachowdhary28) → nobody |
status: | In Progress → Confirmed |
status: | Confirmed → In Progress |
assignee: | nobody → Shikha Chowdhary (shikhachowdhary28) |
Changed in gtg: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This fix works for me.