GTG

"Later" tasks should be less urgent than task without any due date

Bug #491607 reported by Lionel Dricot
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
GTG
Fix Released
Low
Kevin Mehall

Bug Description

This might need some discussion but here's the idea : task without due date should be between soon and later when you order your tasks.

I think that "later" is something we use to say "ok but not now". This makes sense then to put tasks that has not been "rejected later" to appear above.

What do you think ?

Revision history for this message
Kevin Mehall (kevin-mehall) wrote :

One issue with this is that tasks with no due date are not really sorted -- they're just always forced to the end of the list. How should it work when the sort is reversed? Currently, reverse sort puts 'later' tasks on top, and tasks with no date still at the bottom.

Revision history for this message
Bertrand Rousseau (bertrand-rousseau) wrote : Re: [Bug 491607] Re: "Later" tasks should be less urgent than task without any due date

You should have a look at dleft_sort_func in browser.py: this the
function that define the sorting order. By modifying it you should be
able to make "later" tasks coming after tasks with no due date.

On Fri, Dec 4, 2009 at 6:49 AM, Kevin Mehall <email address hidden> wrote:
> One issue with this is that tasks with no due date are not really sorted
> -- they're just always forced to the end of the list. How should it work
> when the sort is reversed? Currently, reverse sort puts 'later' tasks on
> top, and tasks with no date still at the bottom.
>
> --
> "Later" tasks should be less urgent than task without any due date
> https://bugs.launchpad.net/bugs/491607
> You received this bug notification because you are subscribed to Getting
> Things GNOME!.
>

--
Bertrand Rousseau

Revision history for this message
Lionel Dricot (ploum-deactivatedaccount) wrote :

Maybe Kevin could commit for 0.2. If not, report it to 0.3. This is not a release blocking bug.

Changed in gtg:
milestone: none → 0.2
Revision history for this message
Kevin Mehall (kevin-mehall) wrote :

My question was about the expected behavior with descending sort (most distant due date on top). Before, tasks with no due date would remain on the bottom in that view. It's likely not important because there's no real reason to sort that column backwards. I went ahead and made it so no_date is not treated specially -- it's just treated as a date infinitely far in the future, yet before 'later'.

Changed in gtg:
status: New → Fix Committed
assignee: nobody → Kevin Mehall (kevin-mehall)
Changed in gtg:
importance: Undecided → Low
Changed in gtg:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.