Closed Bug 802958 Opened 13 years ago Closed 13 years ago

Tabular reports get improperly result

Categories

(Bugzilla :: Reporting/Charting, defect)

defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: shirphy74, Unassigned)

Details

Attachments

(1 file)

Attached image Snap2.bmp
User Agent: Mozilla/5.0 (Windows NT 5.2) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4 Steps to reproduce: After login bugzilla, click Reports--Tabular reports, and choose Component from Vertical Axis, choose Product from Horizontal Axis, choose SC8810_2.3.5 from product list and generate report, I can get the report result.( SC8810_2.3.5 has more than 100 components and there are more than 10,000 bug with SC8810_2.3.5) But there are some improperly result I can not understand. Actual results: 1, The result contain some component name which are not in SC8810_2.3.5, for example Component APP_DM, but there is a component TJ_APP_DM with SC8810_2.3.5, not APP_DM; by the way, TJ_APP_DM is created by rename APP_DM to TJ_APP_DM. So the component must be TJ_APP_DM, not display APP_DM. 2, There are 539 bugs with component App-NotePad, but when I click 539 to get the bug list, I find that some bugs are in component App-OTA, not App-NotePad ! By click these bug's history, I find the Bug's component change to App-OTA from App-NotePad, that mean the bug's component is App-NotePad before, but now when I am running report it's in component App-OTA. 3, There are many bug catalog to component ---, Why can not display the bug's component just as other component? Is there a limit with the number of component? Expected results: I find the report result is related with the change history of component and bugs. Since I want to get the current result of bug, I hope the result can display report correctly according to current component setting.
This is not a security bug, and it seems something is wrong with your installation. For help, please visit http://www.bugzilla.org/support.
Group: bugzilla-security
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
Can you give me some suggestion in detail about the error? Thanks a lot
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: