On the road to new reports

Here's a look back at recent discussions on the subject of reports. Thank you to those who attended one of the meetings and shared their experiences. Your feedback is important to us, and we'll be using this information to define how reporting will work in the ticketing system we're developing?

The first modifications to reports will be divided into three phases. They will be global, i.e. they will affect all reports, search, navigation and so on. Specific reports will be added or modified in a second phase.

Phase 1

1. Gather reports, lists and statistics under a single tab.
2. Merge reports that share a common subject.
3. Clarify merged report titles.
4. Add a description for each report.

a. First presented as a downloadable document or video.

b. Subsequently, these descriptions will be integrated into the ticketing system.

5. Review the screens leading users to the various reports.

Phase 2

6. Create a search tool by need and/or keywords.

7. Categorize reports by utility or type of role.

8. Standardize table elements for display and export.

9. Add bands of color (or shades of gray) in the background to make it easier to read elements on the same line in tables.

10. Simplify break-even reporting.

Phase 3

11. Add a graph to 3 reports to validate interest.

a. Break-even

b. Sales (to be validated).

c. List of customer labels (customer overview).

2. Save user preferences for the creation of certain reports.

The three phases presented are scheduled to take place over the next year and a half. Of course, they won't be the only developments taking place during this period. In addition, each series of additions will be officially announced via our newsletter.

If you have any questions or comments about the reports, please do not hesitate to contact us.

Note: Some users have mentioned that some current reports appear to show different data when they should normally display the same results. We would like to rectify this situation! Please let us know of any such irregularities. With concrete examples, we'll be able to make the necessary corrections.