Closed Bug 67375 Opened 24 years ago Closed 19 years ago

use sortkeys for priorities

Categories

(Bugzilla :: Creating/Changing Bugs, enhancement)

Product:
Bugzilla
Component:
Creating/Changing Bugs
Version:
2.15
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED
Milestone:
Bugzilla 2.20

People

(Reporter: cls, Assigned: mkanat)

References

Details

Currently, '--' comes before P1 in the sort order.  This means that if the owner
doesn't assign a priority to the bug (usually out of neglect or ambivalence),
then those bugs will stay at the top of everyone's bug list even though they may
not be considered important bugs.
Sorry about the spam. An unset priority should be less than P5.
Priority: -- → P5
I don't think there is UI for configuring this in our installation. Dawn, do you
know? I don't see it in edit|components or edit|params.  Should this go to the
Bugzilla component? If so, as an RFE for configurability?
QA Contact: lchiang → endico
cls, I cannot do this.  Would you like me to morph this bug into a RFE against
Bugzilla to be able to customize the priority field or to sort buglists with ---
at the bottom?
Ok.

nimby
Assignee: asa → myk
Component: Bugzilla: Keyword & Component Changes → Creating/Changing Bugs
Product: mozilla.org → Bugzilla
QA Contact: endico → matty
Whiteboard: DUPEME
Version: other → 2.10
Version: 2.10 → 2.15
Severity: normal → enhancement
Summary: Move '--' further down in priority sort → use sortkeys for priorities
Whiteboard: DUPEME
Target Milestone: --- → Bugzilla 2.18
This is mine.
Assignee: myk → matty
QA Contact: matty → jake
Status: NEW → ASSIGNED
Blocks: 97706
Blocks: 146104
No longer blocks: 97706
Taking Jake's bugs...  his Army Reserve unit has been deployed.
QA Contact: jake → justdave
Enhancements which don't currently have patches on them which are targetted at
2.18 are being retargetted to 2.20 because we're about to freeze for 2.18. 
Consideration will be taken for moving items back to 2.18 on a case-by-case
basis (but is unlikely for enhancements)
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004.  Anything flagged
enhancement that hasn't already landed is being pushed out.  If this bug is
otherwise ready to land, we'll handle it on a case-by-case basis, please set the
blocking2.20 flag to '?' if you think it qualifies.
Target Milestone: Bugzilla 2.20 → Bugzilla 2.22
Dunno, I kinda like having unprioritized stuff show up at the top in my buglist.
 It reminds me to prioritize them. :)

Now that we have user preferences, maybe we just need some way to flag that
"this priority means it hasn't been prioritized" and let the user preference
pick which way to sort it.
Assignee: mattyt-bugzilla → create-and-change
Status: ASSIGNED → NEW
QA Contact: justdave → default-qa
Sortkeys for priorities have been introduced in bug 281876.
Status: NEW → RESOLVED
Closed: 19 years ago
Depends on: 281876
Priority: P5 → --
Resolution: --- → FIXED
Target Milestone: Bugzilla 2.22 → Bugzilla 2.20
No longer blocks: 146104
Depends on: 146104
Assignee: create-and-change → mkanat
You need to log in before you can comment on or make changes to this bug.