User Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20100101 Firefox/10.0.2
Build ID: 20120215223356
Steps to reproduce:
Generate a report with a vertical and a horizontal value. This returns a 2 dimenaional table, with many fields having a count of bugzilla numbers inside.
( e.g. generate with: vertical: QA contact, horizontal: Target milestone)
The table is generated and the number of bug entries in each case is correct.
Also the total is correct.
Now click on any number beside a QA contact ( e.g click on a person who has 3 entries): It returns the correct 3 bugzilla entries. There are 2 more entries for this Target Milestone but for different people.
Now click on the number at the bottom, (which here is 5 entries ) beside the name "Total".
Now it should display the 5 entries from different QA people under this target milestone.
But it does show Zarro bugs found, so no entries are showed.
Reason is that the formulated query contains: ...&qa_contact=Total&...
Due to that, it will never find any matching entry. This part should be removed when clicking on the bugs in the total line, then it works again.
Just found out: only the links on the bottom aren't working.
The links on the left side are correctly working.
This was supposed to be fixed in bug 617676, but it still fails if the vertical axis is a user field. Note that it works fine when using the realname, though. If JS is disabled, URLs are correct too.
Found another problem: when having Product in X and Assignee in Y, then even the links inside the tables aren't working. But here I couldn't yet see the bug in the query.
Created attachment 602397 [details] [diff] [review]
Created attachment 602414 [details] [diff] [review]
My previous patch was wrong.
Comment on attachment 602414 [details] [diff] [review]
Definitely seems to improve things in the scenario described.
Committing to: bzr+ssh://firstname.lastname@example.org/bugzilla/trunk/
Committed revision 8147.
Committing to: bzr+ssh://email@example.com/bugzilla/4.2/
Committed revision 8045.
*** Bug 738238 has been marked as a duplicate of this bug. ***