Closed Bug 357384 Opened 13 years ago Closed 13 years ago

Wrong sorting of Task priority

Categories

(Calendar :: Tasks, defect)

Sunbird 0.3
defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED
Sunbird 0.5

People

(Reporter: djst, Assigned: mattwillis)

Details

Attachments

(1 file, 2 obsolete files)

When sorting your tasks after the priority, this is the result:

1. High Priority items
2. Medium Priority items
3. Low Priority items
4. Unspecified priority items

This gives the impression that Low Priority items have higher priority than unspecified priority items. And why do we need "Unspecified" priority items anyway? That is just a confusing term. Either it has a "Normal" (Medium) priority, or it has higher or lower. New tasks should have Medium priority by default and Unspecified priority should be removed. 

If more granularity is needed, two new priority levels should be introduced: Top/Highest Priority and Lowest Priority.
Current realization tightly follows the iCalendar standard that defines the priority as an integer value in the range [0..9]. The values [1..4] maps to 'high', [5] maps to 'medium', [6..9] maps to 'low' and [0] maps to 'unspecified'. Therefore 'unspecified' needs to be supported.

During sort 'unspecified' is currently sort after all other priorities by purpose (Bug 266602).
> Current realization tightly follows the iCalendar standard that defines the
> priority as an integer value in the range [0..9]. The values [1..4] maps to
> 'high', [5] maps to 'medium', [6..9] maps to 'low' and [0] maps to
> 'unspecified'. Therefore 'unspecified' needs to be supported.

Then by all means support it. But don't place it _below_ low priority items, that just invalidates the Sort by Priority feature.

> 
> During sort 'unspecified' is currently sort after all other priorities by
> purpose (Bug 266602).

AFAIC, the spec doesn't say anything about how to _sort_ 'unspecified' tasks. There's no reason why they should be placed outside the specified priorities. The natural thing is to sort them as 'medium' priority. 

The whole point of sorting a task list by priority is to process tasks in the proper priority order. If the list then presents the lowest priority items _before_ the unspecified priorities, you will end up doing things your boss didn't think was important. 

'Unspecified' should be sorted as 'medium'. See also bug 266602 comment 6.
Attached patch sort unspecified as medium (obsolete) — Splinter Review
Attaching a patch here to force this bug to either be fixed or WONTFIXed.  This makes tasks with unspecified priority sort as 'medium.'  I'm not sure whether it's the right idea from a user-experience point of view, but i'll leave that up to the ui-reviewers.
Assignee: nobody → jminta
Status: NEW → ASSIGNED
Attachment #248034 - Flags: ui-review?(mvl)
Attachment #248034 - Flags: second-review?(mvl)
Attachment #248034 - Flags: first-review?(lilmatt)
Comment on attachment 248034 [details] [diff] [review]
sort unspecified as medium

Moving uirequest to dmose, since this is more a language issue.
Attachment #248034 - Flags: ui-review?(mvl) → ui-review?(dmose)
The workflow I typically use is to add todos quickly while I'm doing other work.  Typically, or at least frequently, I don't get around to assigning a priority to them at the time of creation.  So for me, "unspecified" typically means "untriaged".  And since priorities are generally relative to each other, this means that having untriaged priorities to some degree invalidates existing priorities.  So for my work pattern, at least, this would suggest sorting "unspecified" first, above high.  Comments?
> this would suggest sorting "unspecified" first, above high.
+1

It would at least:
a) Keep them from being lost at the bottom and 
b) Force the user to deal with them if they didn't want them at the top.
OS: Windows XP → All
Hardware: PC → All
Target Milestone: --- → Sunbird 0.5
Attachment #248034 - Attachment is obsolete: true
Attachment #248034 - Flags: ui-review?(dmose)
Attachment #248034 - Flags: second-review?(mvl)
Attachment #248034 - Flags: first-review?(lilmatt)
Attached patch sort no priority above high (obsolete) — Splinter Review
Per comment 5, sorts tasks with no priority _above_ high priority.
This all doesn't matter if we don't sort by priority by default, so I set that.
Assignee: jminta → lilmatt
Attachment #256462 - Flags: ui-review?(dmose)
Attachment #256462 - Flags: second-review?(dmose)
Attachment #256462 - Flags: first-review?(ctalbert.moz)
Props to jminta for noticing I was being silly.
Attachment #256462 - Attachment is obsolete: true
Attachment #256464 - Flags: ui-review?(dmose)
Attachment #256464 - Flags: first-review?(jminta)
Attachment #256462 - Flags: ui-review?(dmose)
Attachment #256462 - Flags: second-review?(dmose)
Attachment #256462 - Flags: first-review?(ctalbert.moz)
Attachment #256464 - Flags: second-review?(dmose)
Attachment #256464 - Flags: first-review?(jminta)
Attachment #256464 - Flags: first-review?(ctalbert.moz)
Do we still need a 2nd review here? And why not push this over to the Sun guys. Their review queues are pretty empty atm.
Comment on attachment 256464 [details] [diff] [review]
Less silly way of doing this

Looks good, tested on windows. My only issue is that there is no way for the user to really know how we are sorting these items. There is no UI indicating that the ! column is the one being sorted on.  But, that is a different issue, IMHO. Should that be a follow on bug? Or is that something we want to address when we "clean up tasks".
Attachment #256464 - Flags: first-review?(ctalbert.moz) → first-review+
(In reply to comment #10)
> (From update of attachment 256464 [details] [diff] [review])
> Looks good, tested on windows. My only issue is that there is no way for the
> user to really know how we are sorting these items. There is no UI indicating
> that the ! column is the one being sorted on.  But, that is a different issue,
> IMHO. Should that be a follow on bug? Or is that something we want to address
> when we "clean up tasks".
> 

I was just about to post the same thing. Someone should probably file a follow up bug to make the "!" column actually show the status. Perhaps an unspecified/untriaged task priority should use a questionmark "?".

On a related notice, clicking in the "!" column area of a task entry should pop-up a simple menu allowing you to set the priority. It is more intuitive than right-clicking and then selecting a sub-menu to change the priority.
Comment on attachment 256464 [details] [diff] [review]
Less silly way of doing this

lilmatt: looks good; ui-r=dmose, r2=dmose.  As far as the other issues mentioned here, they're probably best served by separate bugs.
Attachment #256464 - Flags: ui-review?(dmose)
Attachment #256464 - Flags: ui-review+
Attachment #256464 - Flags: second-review?(dmose)
Attachment #256464 - Flags: second-review+
Patch checked in on MOZILLA_1_8_BRANCH and trunk

-> FIXED
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.