View Issue Details

IDProjectCategoryView StatusLast Update
0007976mantisbtreportspublic2009-06-26 12:07
Reporterzend Assigned Tothraxisp  
PrioritynormalSeverityfeatureReproducibilityhave not tried
Status closedResolutionfixed 
Product Version1.1.0a3 
Fixed in Version1.1.1 
Summary0007976: Convergence Reports System
Description

We would like to have the option to Report By Filter (Project & Versions wise)
For Every chosen Filter

  • Status Report
  • Distribution Report

-- Status Report
For Project X (& SubProjects)
By Date
Cumulative of status:
Open (All status but Resolved, Closed & Suspended)
Resolved
Closed

--Distribution Report
For Projects SubProjects
Every SubProject
By Date
All Open issues (All status but Resolved, Closed & Suspended)
Cumulative of Distribution

TagsNo tags attached.
Attached Files
Distribution Report.JPG (27,535 bytes)   
Distribution Report.JPG (27,535 bytes)   
Status Report.JPG (23,513 bytes)   
Status Report.JPG (23,513 bytes)   

Activities

vboctor

vboctor

2007-05-16 20:54

manager   ~0014546

The description of the requirement here is not very clear to me. Would it be possible to include more details and possible an example that shows a sample output.

zend

zend

2007-05-20 05:36

reporter   ~0014563

We would like two types of graph reports that the base data (Projects $ Versions) is driven from a selected filter.
The first graph we are looking for is “Status Report” similar to the current “Cumulative By Date” just with the status: Open (All status but Resolved, Closed & Suspended), Resolved & Closed.
The second is “Distribution Report” similar to “By Category” but for every Subproject and show status of All Open issues (All status but Resolved, Closed & Suspended)

vboctor

vboctor

2007-05-26 00:54

manager   ~0014641

Your reports have a time dimension which we don't have a well structured data for. For some of the data like status changes, we can probably hack it using the issue history. However, for distribution it is not as easy since this is not in the history. Also the history is not designed to be a feature to base reporting on. I don't think it will scale with huge data since the data is not a format that can be easy aggregated using SQL.

Sometime ago I have written some requirements relating to this issue. The idea is to regularly aggregate the data and make such aggregated data available for reporting:
http://www.mantisbt.org/wiki/doku.php/mantisbt:performance_counters_requirements

whobe

whobe

2007-08-16 00:48

reporter   ~0015438

We would also like this ability to create a filter that is for resolved issues that are not suspended. This ability to add not would be good for other filter items as well.

thraxisp

thraxisp

2009-05-19 21:53

reporter   ~0021847

The code for this feature was submitted in late 2007.