Hi Joe, Sorry for going silent for all these days. I had exams.
Coming back to the implementation of the project. I am not sure all of it can be done in the specified time. But I hope to generate as many reports as I can. As I replied in some other thread, I think I can generate most of the reports periodically using the TracCronPlugin[1] and once they are generated, it shouldn't be tough to serve them as a separate page or to mail them or to exposing them as widgets. The only problem I see is, the plugin is not under active development. And I am not sure if you are okay with using it(license etc..). I am trying to see the one's I can complete in the time span. If you still think this is overly ambitious, I will stick back to the projects I've been talking about. Regards, Shiva Teja. On Tue, Apr 23, 2013 at 4:31 PM, Joachim Dreimann < [email protected]> wrote: > Hi Shiva, > > There's a 'Reports' tool already that users can navigate to from a link on > the right of the breadcrumb on ticket pages (as opposed to Wiki and Source > pages): > https://issues.apache.org/bloodhound/report > > Currently reports are just saved custom queries (you can build those here > for example:[1]) with the ability to define custom SQL or TracQueries. > > A common use case in organisations is to report on changes over time, so a > particular use case for time series reports could be to show data for: > - Weekly number of open tickets by type for <product x> > - Daily number of tickets by resolution type > > Another use case would be to query the status at a fixed point in the past, > like: > - Tickets assigned to <user x> on <date> > > There is plenty of scope for meaningful default queries, such as: > - Abandoned tickets (those that have not been modified for a long time, or > which the owner was removed from recently without replacement) > - Trouble tickets (those with much more activity than the average, or > active for much longer) > > Graphing and charts is not a requirement for this, tables of information > would already be helpful. It would be a bonus however. > Notifications are also an optional extra: Users may want to receive a > regular email update containing the latest information (including some > historical information for reference), or automatically report on a > projects progress to their boss every week. That could include for example > a list of the 5 highest priority/severity tickets closed during the current > week, and the 5 highest priority/severity ones that remain open. > > I hope that helps you as a starting point. Again a basic implementation > would be an upgrade to the reports page, a more advanced one would include > exposing this as embeddable objects and widgets in Bloodhound itself. > > You can probably tell from the above that there is a wish list far longer > than is feasible to implement during one GSoC project. It's more important > to us that you pick a scope that you feel comfortable with completing than > one that is overly ambitious and will be too difficult to complete in the > given time. > > Cheers, > Joe > > [1] https://issues.apache.org/bloodhound/query > > > On 21 April 2013 20:09, Shiva Teja <[email protected]> wrote: > > > Hi, > > > > After a bit of discussion on the irc I said that I'll be working on 3 > small > > projects for GSoC (Social Cards Integration (#480), Embeddable tickets/ > > objects(#479) and a wiki to text functionality). > > > > Currently I am planning to work on "Add Time Series Reports(#489)". I > might > > need a little more clarification on this. What are some general > information > > queries(?) on the reports ? Any pointers to such existing > functionalities > > should also be fine. > > > > Regards, > > Shiva Teja.(irc: teja) > > > > > > -- > Joe Dreimann | *User Experience Designer* | WANdisco< > http://www.wandisco.com/> > > @jdreimann <https://twitter.com/jdreimann> > * > * > *Join one of our free daily demo sessions on* *Scaling Subversion for the > Enterprise <http://www.wandisco.com/training/webinars>* > > THIS MESSAGE AND ANY ATTACHMENTS ARE CONFIDENTIAL, PROPRIETARY, AND MAY BE > PRIVILEGED. If this message was misdirected, WANdisco, Inc. and its > subsidiaries, ("WANdisco") does not waive any confidentiality or privilege. > If you are not the intended recipient, please notify us immediately and > destroy the message without disclosing its contents to anyone. Any > distribution, use or copying of this e-mail or the information it contains > by other than an intended recipient is unauthorized. The views and > opinions expressed in this e-mail message are the author's own and may not > reflect the views and opinions of WANdisco, unless the author is authorized > by WANdisco to express such views or opinions on its behalf. All email > sent to or from this address is subject to electronic storage and review by > WANdisco. Although WANdisco operates anti-virus programs, it does not > accept responsibility for any damage whatsoever caused by viruses being > passed. >
