REST-API /summary

The current REST-API has a hard-coded /summary endpoint that displays
a summary of open issues. The class and query to use is hard-coded.

Now I do run several trackers where we either don't have an issue-class
at all or have several issue-like classes, 'issue' being just one of
them.

So what is displayed as the summary should probably not be hard-coded.
Now before I implement something that later has to be changed: Should we
make this configurable in config.ini? We currently *do* have the default
class for the mail gateway in config.ini (which by default is 'issue'),
we could uses something similar for the rest-api but would need some
more configuration to specify the query to use.

Ideas, Wishes?

Or should we drop the /summary altogether?
(would be my favourite)

Ralf
-- 
Dr. Ralf Schlatterbeck                  Tel:   +43/2243/26465-16
Open Source Consulting                  www:   http://www.runtux.com
Reichergasse 131, A-3411 Weidling       email: [email protected]