Differences

This shows you the differences between two versions of the page.

--- mantisbt:reporting_requirements [2006/09/22 10:53] – created (posted on behalf of Rolf Kleef) siebrand
+++ mantisbt:reporting_requirements [2011/11/16 07:37] (current) – The page rendering was broken (maybe since new PHP version on mantisbt.org). Added new line to fix it at end of file. atrol
@@ Line 1: / Line 1: @@
+====== Reporting Requirements ======
+**Author:** Rolf Kleef
+===== Introduction =====
+When using Mantis as a management tool, for example for SLA's (Service
+Level Agreements), a user (often a project manager) needs to be able to
+create more types of reports.
+===== Report per period =====
+As a project manager,
+I want to create a report of all issues over the last month/quarter/year
+So that I can send this to my client as report on our SLA
+The report should provide statistics per severity, and offer a list of all
+issues, including self-defined fields (title, reporter, summary, ...).
+Example: send the full list of issues to a client, so that they can review
+it, and see where input from their side is still needed. After review, all
+resolved tickets can be closed.
+===== Response and resolution times =====
+As a project manager,
+I want to create a report on response and resolution times
+So that I can send this to my client as report on our SLA
+This will need some further discussion on how to measure those times. The
+response time could be the amount of time the issue has been "New", but the
+resolution time is more complex. For instance, waiting for essential input
+from a client may not be counted in the resolution time.
+Also, the reporting should be done per severity, or focus on
+response/resolution times not being within agreed boundaries (this would
+need to be a new user story).
+===== Project manager dashboard =====
+As a project manager,
+I want to have an overview of issues and deadlines
+So that I can take action in time on issues that may be problematic
+This partly is discussed in the [[Due Date Requirements]]. Maybe together
+with estimated efforts (current "projection" field?). It would be nice to
+also group this by assignee, as a step towards workload reporting.