Open
Bug 122755
Opened 23 years ago
Updated 14 years ago
allow user to specify grouping of bugs
Categories
(Bugzilla :: Query/Bug List, enhancement)
Tracking
()
NEW
People
(Reporter: myk, Unassigned)
Details
In addition to specifying a sort order, it should be possible to specify a field by which bugs in the bug list should be grouped and then generate bug counts across each group in addition to listing the total number of bugs.
Reporter | ||
Updated•23 years ago
|
Severity: normal → enhancement
Reporter | ||
Updated•23 years ago
|
Summary: allow using to specify grouping of bugs → allow user to specify grouping of bugs
Comment 1•23 years ago
|
||
Sounds like what I want to do for general summary reports (bug #12282).
Comment 2•23 years ago
|
||
Myk, do you think this is similar to bug 77764 (see attachment 48826 [details])?
Reporter | ||
Comment 3•23 years ago
|
||
Andreas, it's quite similar, but not the same, since in this bug I don't propose collapsing the list into merely a count but rather showing the whole list with counts for each group.
Comment 4•23 years ago
|
||
So should the counts for each group be displayed in the list, or separately? a) bug 12345 cri foo@foo.com hello world bug 23456 enh foo@foo.com bla bla bla 2 bugs bug 34567 maj bar@bar.com abc def ghi bug 45678 nor bar@bar.com a;sldkfja;lsdfjlasdjf bug 56789 min bar@bar.com sdkjsdfjkfjksdfjkfjksdfjksdfjk 3 bugs or b) bug 12345 cri foo@foo.com hello world bug 23456 enh foo@foo.com bla bla bla bug 34567 maj bar@bar.com abc def ghi bug 45678 nor bar@bar.com a;sldkfja;lsdfjlasdjf bug 56789 min bar@bar.com sdkjsdfjkfjksdfjkfjksdfjksdfjk foo@foo.com: 2 bugs bar@bar.com: 3 bugs Or are you thinking of something else?
Reporter | ||
Comment 5•23 years ago
|
||
I'm thinking of version a (in the list).
Comment 6•22 years ago
|
||
Moving to 2.18, but I'm not sure what's covered here but not on bug #12282.
Priority: -- → P4
Target Milestone: --- → Bugzilla 2.18
Comment 7•22 years ago
|
||
It would be useful to be able to group by more than one field, because in some situations (finding out how busy people are with each project etc.) you really need to get more info. Grouping by both assignee and product would help me a lot, and another regularly useful combination would be product and resolution (combined with a milestone search condition).
Updated•21 years ago
|
Assignee: endico → nobody
Comment 8•20 years ago
|
||
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
Comment 9•20 years ago
|
||
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
Comment 10•19 years ago
|
||
The trunk is now frozen to prepare Bugzilla 2.22. Only bug fixes are accepted, no enhancement bugs. As this bug has a pretty low activity (especially from the assignee), it's retargetted to ---. If you want to work on it and you think you can have it fixed for 2.24, please retarget it accordingly (to 2.24).
Target Milestone: Bugzilla 2.22 → ---
Updated•18 years ago
|
QA Contact: mattyt-bugzilla → default-qa
Updated•16 years ago
|
Assignee: nobody → query-and-buglist
Priority: P4 → --
You need to log in
before you can comment on or make changes to this bug.
Description
•