Closed Bug 279590 Opened 20 years ago Closed 20 years ago

using QA Contact for Z-axis on bar report creates duplicate images instead of unique ones

Categories

(Bugzilla :: Reporting/Charting, defect)

2.18
x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 281503

People

(Reporter: jdglanville, Assigned: gerv)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113

When creating a multi-image bar chart in Bugzilla 2.18rc3, where QA Contact is
the Z-axis, then the resulting charts are all duplicates of the 'Total'
(final/aggregate) chart.

Reproducible: Always

Steps to Reproduce:
1. goto Reports - Graphical Reports
2. set Vertical Axis = Priority
3. set Horizontal Axis = Target Milestone
4. set Multiple Images = QA Contact
5. set Format = Bar Graph
6. Generate Report
Actual Results:  
I receieved several bar charts, one for every QA Contact.  However, all the
charts were identical.

Expected Results:  
What should have happened is that the multiple bar charts should have been unique.

I've tried some variables (not combined):
- it doesn't actually matter what the horizontal or vertical axises are.
If I change the horizontal to severity, the problem still exists.
- it doesn't matter what the format is.  If I use line charts, all
images are still the same.
- if I change the format to table, I get different tables (as expected).
- if I change the Multiple Images value to anything else (like
Assignee), then I get different images, as expected.

Basically, in a nutshell, if I try to create a graphical charts using QA
Contact for the Z axis, then all the multiple charts are the same as the
TOTAL chart.
Version: unspecified → 2.18
Bug 281503 has more analysis, so marking dupe.

Gerv

*** This bug has been marked as a duplicate of 281503 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.