Submissions Statistics

[evilaliv3]

This ticket is to keep track about the collection of requirements for the implementation of submissions statistics.

From the current analysis the information that would be useful to collect and the useful user interface for visualizing the data are:

• The number of received submissions: Statistics about number of submissions for admins #2816
• The state for the submissions and a percentage for each stat (new, archived, deleted);
• The average time of recipient answers to whistleblower actions;
• The average time of closure of the submission (from the state new to the state archived or deleted)
• Number of interactions with the whistleblower;
• A breakdown of submissions by labels;
• A breakdown of submissions by status (new, archived, deleted);
• A breakdown of the submission based on answers to dropdown questions;
• Number of unanswered tips and average response times to comments/messages and uploads;
• Statistics about returning whistleblowers: Make it possible to read statistics about returning whistleblowers #3346;
• Statistics for anonymous connections (Tor), confidential connections (HTTPS)

It would be interesting to be able to show this statistics enabling users to create reports:

• filtering data by date/period
• filtering data by reporting channel

It would be interesting to be able to export statistics in the following format:

• web visualization of the statistics on the application
• raw export of data in CSV format
• raw export of the data in XLS forma
• professional output of data in PDF format

[elbill]

I have amended the requirements based on the initial work of @evilaliv3

• The number of received submissions;
• The average time of recipient answers to whistleblower actions;
• The average time of closure of the submission (from the state new to the state archived or deleted)
• Number of interactions with the whistleblower;
• Number of unanswered tips or new WB messages and average response times to comments/messages and uploads;
• A breakdown of submissions by labels; (all #hachtags labels should be counted)
• A breakdown of submissions by status and a percentage for each status (new, ….. , deleted);
• A breakdown of the submission for one or more of the questionnaire drop down questions

The above results should be able to be parameterized by
• Context
• Analyze statistics of reports that are filtered through the filtering feature of the CMS ….

We have to see if there is some way of exporting all non sensitive information out of the platform in CSV format (not the text boxes of free text information tha t may contain personal data but pull down menus or other non sensitive information)

[evilaliv3]

Thank you @elbill for your feedback.
I extended my initial message including all this feedback.

I consider that the set of features to be included is well defined and suggest.
If you want to discuss the specific tickets and facilitate developers i suggest that we could try to create specific tickets to divide the work and furtherly specify each feature with more detail.