Certain key categories (IPs, abuses, ...) in pie chart dataset tables have associated context search actions that provide user with ability to quickly search different parts of the application. (Redmine issue: #4321)

It is now possible to use main logger from within the Jinja2 templates.

All blueprints can similarly to registering menu entries register context search actions for one or more groups. These are then used for generating context search action dropdown menus for various items like IP addresses, groups, etc. One of the example use cases is the event search result page, which contains action search menus for each of the displayed IP address, abuse group, category, etc. (Redmine issue: #4321)

Sorry, previous fix was not correct.

(Redmine issue: #3361,#4570)

There was an invalid expression in the algorithm. Also the setdefault method is much more convenient than previous solution.

The warning setting results in additional and unnecessary email being sent in case the module is executed from cron.

Radko Krkoš authored 6 years ago and Jan Mach committed 6 years ago

Enumeration tables used to speed up enum generation for filtering were incorrect as multiple NULL values could have been inserted increasing the table size over time. This affected the enumerations for non-array parameters only. As the 'any value' and 'without value' options are added automatically, we can disable support for NULLs, fixing the growing tables.

(Redmine issue: #4367)

(Redmine issue: #4321)

(Redmine issue: #4321)

It has special meaning, it does not belong to any data series. (Redmine issue: #4321)

After previous changes the statistics panel in report detail view needed to be updated as well. I have also unified HTML coding style to match other similar views (eg. event dashboard view). (Redmine issue: #4321)

Various secondary statistics like counts, minimums, maximums and sums were pre-calculated together with regular statistics. These operations do not make sense anymore from multiple point of views:
- They are not used during chart generation anymore, because these values are calculated by JavaScript code.
- They do not make sense during merging statistical data, because they produce incorrect results anyway (for example without knowing the exact omitted values it is not possible to calculate the counts, averages, minimums etc.).

(Redmine issue: #4321)

Translated recently implemented features. (Redmine issue: #3387)

(Redmine issue: #4321)

(Redmine issue: #4321)

(Redmine issue: #4321)

Added missing pie charts containing totals to all timeline charts. Hidden the abuses panel from external processing statistics display. (Redmine issue: #4321)

(Redmine issue: #4321)

Unified style of HTML code for event, reporting and timeline dashboards. Improved documentation of Jinja2 chart macros. Refactored some macro names for better code readability. (Redmine issue: #4321)

Improved all related Jinja2 macros. Moved as much functionality as possible to plain JavaScript code to reduce the amount of code that was being parametrized and generated from Jinja2 templates. (Redmine issue: #4321)

Improved all related Jinja2 macros. Moved as much functionality as possible to plain JavaScript code to reduce the amount of code that was being parametrized and generated from Jinja2 templates. (Redmine issue: #4321)

Instead of coloring the call background insert small circle icon with color corresponding with related dataset. (Redmine issue: #4321)

In previous implementation the pie charts and their apropriate dataset tables were generated separately. Now the table is also generated by D3 and all of this is neatly encapsulated in Jinja2 macros similarly to rendering of timeline charts. (Redmine issue: #4321)

(Redmine issue: #4321)

Common charts within tab panels are used for displaying statistics for reporting, event dashboard and event timeline. I have implemented Jinja2 macros for rendering these tab panels and their appropriate navigation. (Redmine issue: #4321)

(Redmine issue: #4321)

There was an issue with the Globalize library being used before it was fully initialized. This issue is now solved by using synchronous AJAX get requests to fetch the configuration JSON metadata files, this solution is however not optimal and should be revisited in the future. (Redmine issue: #4321)

(Redmine issue: #4321)

Minor JS code optimalizations and documentation and style improvements. (Redmine issue: #4321)

(Redmine issue: #4321)

Table footer now contains following information: cnt, min, max, sum, avg, median for each of the data series in the table dataset. (Redmine issue: #4321)

The timeline chart dataset tables now have localized header titles and numbers in the table are localized with Globalize. (Redmine issue: #4321)

(Redmine issue: #4321)

(Redmine issue: #3387)

Implemented prototype of collapsible dataset view and downloadable dataset option for timeline charts.

All timeline charts in reporting dashboard and timeline module now support displaying of chart datasets in tables within collabsible sidebar. Additionaly the chart dataset can now be downloaded as CSV file for easy import into table processor software like LibreOffice. (Redmine issue: #4321)

This was done to avoid duplication of titles in case there are more charts providing view to the same data. (Redmine issue: #4321)

(Redmine issue: #4321)