122755 - allow user to specify grouping of bugs

Status: NEW

(Bugzilla :: Query/Bug List, enhancement)

Description

[Myk Melez [:myk] [@mykmelez]]

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.

Comment 1

[Matthew Tuck [:CodeMachine]]

Sounds like what I want to do for general summary reports (bug #12282).

Comment 2

[Andreas Franke (gone)]

Myk, do you think this is similar to bug 77764 (see attachment 48826 [details])?

Comment 3

[Myk Melez [:myk] [@mykmelez]]

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

[Andreas Franke (gone)]

So should the counts for each group be displayed in the list, or separately?

a) bug 12345 cri [e-mail] hello world
   bug 23456 enh [e-mail] bla bla bla
   2 bugs 
   bug 34567 maj [e-mail] abc def ghi 
   bug 45678 nor [e-mail] a;sldkfja;lsdfjlasdjf
   bug 56789 min [e-mail] sdkjsdfjkfjksdfjkfjksdfjksdfjk
   3 bugs

or

b) bug 12345 cri [e-mail] hello world
   bug 23456 enh [e-mail] bla bla bla
   bug 34567 maj [e-mail] abc def ghi 
   bug 45678 nor [e-mail] a;sldkfja;lsdfjlasdjf
   bug 56789 min [e-mail] sdkjsdfjkfjksdfjkfjksdfjksdfjk

   [e-mail]: 2 bugs
   [e-mail]: 3 bugs

Or are you thinking of something else?

Comment 5

[Myk Melez [:myk] [@mykmelez]]

I'm thinking of version a (in the list).

Comment 6

[Matthew Tuck [:CodeMachine]]

Moving to 2.18, but I'm not sure what's covered here but not on bug #12282.

Comment 7

[Jouni Heikniemi]

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). 

Comment 8

[Dave Miller [: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)

Comment 9

[Dave Miller [:justdave]]

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.

Comment 10

[Frédéric Buclin]

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).