Re: Advanced Reporting

Hi,

Well, I am no thinking un use mantis to control a software development process, so I think I can´t help you too much.
I would be nicer -IMHO- if you provide the controls created by you QA-Team so we could see if there is any option to improve them.
From the point of view of a QA-Team, I think they will be interested on... (few ideas):
 - time control.
 - workload. (by weeks, techs, months, escalations, customers, products...)
 - reopened cases (in oder to improve the KB with solutions for well-know problems)
 - open/close ratio (to avoid backlog)

I don´t know if you are using those values at this time, let me know.
I also think it could be a very good idea if you can involve the QA-Coordination team, but I don´t know if this mailing list would be the best place or if a new thread should be created outside.

The idea of the report must be simple:
 - Reports should be always avaible via web interface.
 - Techs must be able to see their metrics (tech. dashboard). Real time should be ok, but a job cron every X hours to update them can be useful too.
 ;- Extended reports (global dashboards) with global metrics (all techs, all cases, backlog...) only must be available to team leaders, qa-coordinators...
 - All reports must be able to be exported to .csv
 ;- Graphics are a must, they are very important if the reports are going to be reviewed by managers or non-technical people.

Maybe I am wrong with this ideas, maybe not, anyway, let me know what do you think.