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
