179581 - Add reporting on keywords to new reporting system

Status: RESOLVED FIXED

(Bugzilla :: Reporting/Charting, enhancement, P3)

Description

[Heikki Toivonen (remove -bugzilla when emailing directly)]

I asked for report assignee/keywords in table format, and Bugzilla made
a column for every _combination_ of keywords. It should be so that it
will only give me one column for each keyword.

There might be other reports where this applies as well.

Comment 1

[Gervase Markham [:gerv]]

Can you please give me a URL example? This doesn't happen on my test installation.

Gerv

Comment 2

[Heikki Toivonen (remove -bugzilla when emailing directly)]

See URL. Rows should be the people in my team, and columns should be keywords,
limited so that the keyword is any of topembed,topembed+,nsbeta1,nsbeta1+ (so
there should be 4 columns for keywords, but there are 23).

Comment 3

[Bradley Baetz (:bbaetz)]

Note that regexp searches are inefficient; you'd be better of searching for 'is'
'[e-mail]' or 'is' '[e-mail]', and so on.

Alternately, you can use 'assignee' 'anyexact'
'[e-mail],[e-mail],[e-mail]' in the boolean charts, which is
much much more efficient. This option isn't in the ui (bug 179302), but since
this particular query is probably a bookmark, just create it frrom the query pge
using some other condition, such as equals, and then manually modify the url
param from 'equals' to 'anyexact'.

Anyway, for this problem, the issue is that we're selecting bugs.keywords, which
is the keyword cache, and jsut a string. I'm not sure how to fix this. You could
select the keyword id instead, but we GROUP BY bug_id, so that won't work. If we
fixed bug 179322 then the grouping would be in the inner query, and you could
get all teh entries in the outer one. The totals may be a bit odd, though, since
you'd be couting keyword occurences, not bugs. OTOH, that may be what is expected.

(The other option, hacking reports.cgi to speccialcase keywords, is a massive
hack, and won't work with custfields anyway, where this sort of thing will just
be more generic)

Thoughts?

Comment 4

[Bradley Baetz (:bbaetz)]

Actually, thinking about this a bit more, fixing bug 179322 really is the way to
go. This would allow us to kill the horribly ugly keyword cache while we were at it.

Comment 5

[Gervase Markham [:gerv]]

I'm going to remove keywords from the available list in the mean time, because
the current implementation just causes confusion.

(Incidentally, the reason I didn't see this in testing is because my test DB
doesn't have any bugs with more than one keyword.)

Gerv

Comment 6

[Gervase Markham [:gerv]]

Bug 180205 removed keywords from the list in the mean time.

Gerv

Comment 9

[Frédéric Buclin]

This has been implemented in Bugzilla 4.5.2 thanks to bug 863745.