Improved documentation with focus on possible developers, so the Overview and Development section were greatly improved. (Redmine issue: #3361)

System status now displays internal daemon component counters. Current implementation is however proof-of-concept only, because it will not display correctly counters for paralelized daemon modules. (Redmine issue: #4218)

There were some outdated commands. Fixed wrong find commands (asterisks required quoting). (Redmine issue: #3387)

* Integrated item changelogs into filter detail view.
* Integrated item changelogs into network detail view.
* Integrated item changelogs into group reporting settings detail view.
* Integrated subitem changelogs into group detail view. Besides group item changelogs the changelogs for all filters, networks and settings are displayed on the group detail page.
* Integrated item changelogs into user detail view.
* Integrated changelogs where particular user is the author of the change into user detail view as actionlogs.
* Translated all newly added strings into czech language.

(Redmine issue: #4219)

(Redmine issue: #3387)

(Redmine issue: #3443)

It was impossible to store the 'state' attribute of user, group and filter objects into PostgreSQL database, because it was not correctly converted to boolean and SQLAlchemy failed to generate proper SQL command.

Instead of appending build number to version string only for development suite packages, the buildnumber will now not be appended only to production level packages and will be present in any other cases. (Redmine issue: #3387)

On some versions of PostgreSQL the mogrify method returns differently formatted strings (extra space in after comma in lists). This needed to be fixed. (Redmine issue: #1017)

It is up to the developer to ensure that pybabel binary points to correct version of babel. (Redmine issue: #3387)

It is up to the developer to ensure that babel binary points to correct version of babel. (Redmine issue: #3387)

(Redmine issue: #3387)

(Redmine issue: #3387)

(Redmine issue: #3443)

(Redmine issue: #3387)

Based on the feedback from users it is much more usefull to display timestamps in event report sections in format that can be copied and directly used in third party systems instead of adjusting the localized display. New Jinja2 function was implemented to provide this new feature in report templates.

Added information about how to get rid of old Perl-based Mentat system and other now unnecessary files and directories. (Redmine issue: #3361)

(Redmine issue: #3361,#3387)

(Redmine issue: #3387)

In case there were no new events fetched from database and some events relapsed, the filtering result was not available and there was no default when constructing the report object.

The only places in documentation where MongoDB mentions were kept are for obvious reasons installation and migration pages. (Redmine issue: #4225)

(Redmine issue: #3387)

(Redmine issue: #3361)

The authentication needed to be turned off to enable unauthenticated access to report data. There is still random string in report identifier, which provides some security similar to unauthenticated access. (Redmine issue: #4240)

(Redmine issue: #3387)

Added unit test for testing method for saving attachments into JSON file. (Redmine issue: #1017,#4237,#4229)

Thresholding cache provides better logs, sot that administrator has better ability to verify correct functionality. (Redmine issue: #4237)

(Redmine issue: #4237)

When calculating statistics, only summary reports should be considered. Otherwise some of the data can get calculated more than once and statistics are mangled. (Redmine issue: #4237)

By adding the total number of all generated reports and separate counters for summary and extra reports one will have better insight into the reporting performance. (Redmine issue: #4237)

(Redmine issue: #3387)

Added section about cleanup into migration documentation page plus few additional minor improvements.

(Redmine issue: #3361)

This commit marks the first production release of Mentat system 2.0.0. After lots of work we have finally successfully abandoned the original implementation written in Perl and using MongoDB as database backend.

This commit also marks the end of an era of frantic coding. Until now some of the guidelines and best practices for coding and committing were violated in favor of faster development. This was also possible thanks to the fact that there was mostly only single developer working on the project, so there were no possible conflicts. From now on however things will be back to normal state.

(Redmine issue: #3387)

(Redmine issue: #3377)

(Redmine issue: #3377)