Bug 190684

Summary:	Reports has no idea what categories exist or wtf is going on with them
Product:	Services	Reporter:	Eitan Adler <eadler>
Component:	Bug Tracker	Assignee:	Bugmeister <bugmeister>
Status:	Closed Not Accepted
Severity:	Affects Only Me	CC:	mva
Priority:	---
Version:	unspecified
Hardware:	Any
OS:	Any
Bug Depends on:
Bug Blocks:	190631

Description Eitan Adler freebsd_committer

2014-06-06 00:14:27 UTC

- New reports seem random and unrelated as to what they allow/don't allow to be shown.  Its not even clear they are generating correct reports

- Old reports don't work at all.

Comment 1 Marcus von Appen freebsd_committer

2014-09-13 09:15:20 UTC

One of the problems is the inconsistency with historical information from bugs_activity. The status changes within bugs_activity use the old status or even broken information imported from GNATS.

We have e.g. status like 

* closed ... bug in gnats or sed opened (yes, seriously)
* feedback timeout
* patched
* open
* closed
* repocopy

which do not match against the current status and resolutions This makes meaningful reporting close to impossible, since the data miner (collectstats.pl) just picks that historical information and does weird things with it. This also leads to lots of confusing options to be selected from in the report web pages.

We need a larger clean-up of the imported GNATS data to make the builtin reporting work as intended.

Comment 2 Marcus von Appen freebsd_committer

2014-11-23 14:29:33 UTC

The new reports do not support aggregating data that was entered prior to the creation of the report itself. This makes them useless for reports that shall provide accurate figures over time (see https://bugzilla.mozilla.org/show_bug.cgi?id=1103558 for that issue).

The old reports should provide correct figures with the last update to Bugzilla (except for In Progress, see bug 190631).

I'm closing this issue, since we can't solve this, but either have to provide our own reporting or stick to the old charts for now.