On 20 Jun 2013, at 23:30, Hua Xiang <[email protected]> wrote: > Hi! > Many thanks to the developers who attended this meeting. > This meeting is about the requirements analysis of the Bloodhound reporting > function. > The requirements were combined and summarized as follows: > 1. scope of reporting > > - reports for developers > - daily report, e.g., "start of day" lists the new opened tickets of > the day etc. > - weekly report, e.g., "week in review" lists the tickets closed of > the week etc. > - reports based on components, e.g., open tickets per department, > tickets closed in the last week, percentage of ticked closed in terms of > the level of priority etc. > - reports for all users > - according to a given timeslice and a specific query, lists the > historical information > > 2. form of output : via email or webpage, presented in table or in graph > > Is there any missing, unambiguous, conflict or complement? > > Cheers! > Hua
I feel some more context is necessary for this message to make sense: As Hua's mentor I arranged for her to meet someone who uses Bloodhound for daily and weekly reporting. She met him (and some others) today, and I asked her to summarise what she learned so it could help others on the dev@ list as well. - Joe
