73004 - Periodic reports.

Status: RESOLVED DUPLICATE of bug 185090

(Bugzilla :: Email Notifications, enhancement)

Description

[Matthew Tuck [:CodeMachine]]

Bugzilla should allow the admin to set up periodic reports.

These should be either bug lists or, when implemented, general summary reports
(bug #12282).  You would need to be able to specify the columns that appear, so
it might be best done in conjunction with column specification report on
standard queries (bug #12284).

For HTML, you should specify them using the same output panel that appears in
the query page (or summary report page).

For each periodic report, you should be able to specify a period in days (one
cron job should run each night and do all reports at once).

You also should be able to specify a header for the report in either text or
HTML.  Ideally a user could specify which form they wanted, the admin specifies
it in HTML, and Bugzilla would convert to text for users who desire it.

And finally, you need to determine who gets the report.

This will either be based on the bug's data, and therefore you specify a set of
fields.  Anyone who appears in these fields gets the report.

Similarly you might specify it goes to the component owner and/or QA.

Alternatively, you could specify a fixed list of users.  It would be good if
relatively unprivileged people could specify their own reports, but maybe they
would have to be in a group (similar to confirm) to do this.  Maybe they would
be restricted to the report being sent to themselves.

Currently we have whineatnews, so I'll target this for 3.0 for the moment since
we might want to be general straight off rather than reimplement code that isn't
reusable.

Other possible uses are whining about passed milestones (bug #65388), whine
about votes on resolved bugs (bug #27553) and periodic reports about untargetted
bugs (bug #68991).

Also existing is whining on mismatch on milestone/priority between dependent
bugs (bug #16743), but that is not totally intra-bug, so it might be good to add
general querying on the attributes of dependent bugs in either direction (which
would be quite useful in itself).

Comment 1

[Hixie (not reading bugmail)]

whineatnews is unbelievably unpopular. ;-)

I doubt this will make the 3.0 train. I'll move it off to 3.2, but I'll make 
sure that I don't make it impossible to implement this.

Comment 2

[Matthew Tuck [:CodeMachine]]

So I take it whineatnews will be an exception to the "implement all 2.X
functionality" then.

Comment 3

[Matthew Tuck [:CodeMachine]]

We should emit whinemails when required constraints on a bug are not satisfied.
 These would probably go to the administrator.  However this might fit in with
the existing sanity check system.

If we mail the whole report to one person things are rather easy.  Personal
reports should go to the person who owns them.  Group reports (set up by someone
with the privilege to create reports for that group) should be able to go to
anyone in the group.  System reports (set up by someone with the privilege to
create reports on the system) should be able to go to anyone.

But what if the reports are based on the actual bug - ie different parts of the
report go to different people depending on what bugs they are on.  If it's a
system report - no problem.  But if its a group report you can create reports
that go to people outside of the group, and if it's a personal report you can
create reports that go to other people.

Perhaps we should make it that parts of the report that would go outside of the
group/to another person simply aren't generated.

Comment 4

[Matthew Tuck [:CodeMachine]]

We could also distinguish reports that are compulsory from reports that are
opt-in or opt-out.

Comment 5

[Matthew Tuck [:CodeMachine]]

Moving to new Bugzilla product ...

Comment 6

[Dave Miller [:justdave]]

Changing default owner of Email Notifications component to JayPee, a.k.a.
J. Paul Reed ([e-mail]).  Jake will be offline for a few months.

Comment 7

[Shane H. W. Travis]

(Technically, bug 185090 is a dupe of this one... but since that one's RESO/FIX 
while this one is old and abandoned, I'm going the other way.)

*** This bug has been marked as a duplicate of 185090 ***

Comment 8

[Dave Miller [:justdave]]

clearing target of DUPLICATE/WONTFIX/INVALID/WORKSFORME so they'll show up as
untriaged if they get reopened.