To implement this functionality following changes were necessary:
* Add new association table to keep track of wanted memberships.
* Changed prototype for item action authorization and change method to enable multiple parameters.
* Merge GuiUserModel with UserModel to make objects comparable.
* Implemented new base class for easy implementation of relation views.
* Implemented new endpoints for group membership management.
* Added new action buttons to users list in group detail view.
* Added new action buttons to group list in user detail view.

(Redmine issue: #5762)

(Redmine issue: #4518)

Context search action groups are now more specific for searching from event dashboards and report detail, the dt_from and dt_to parameters are now pre-filled with available values. This patch also fixes the long lasting bug in DateTime search form fields. (Redmine issue: #5341,#4518)

E
So far the applicatin menu supported only one contextual parameter, item. This was very restricting, because it did not allow menus to generate more complex links. (Redmine issue: #5341)

(Redmine issue: #4500)

Chart toplists for dashboards are now calculated in the frontend in Javacript instead of in background in Python. This approach will enable users to access the full information, which is necessary in some use cases. (Redmine issue: #4486)

Datetime in json structured_data is now store in utc timezone, change to report timezone is done in templates. (Redmine issue: #4499)

Feedback data are validate while sending, feedback on web is as form, small visual changes to uniformalize visual style. (Redmine issue: #4501)

Lightweight feedback functionality for reports. Feedback is send to addresses from config file with information about logged user. Without feedback for users that are not logged-in. Feedback info is not stored permanently. (Redmine issue: #4501)

On-fly generating of report messages on hawat side (Redmine issue: #4498)

I have used Pylint tool to fix easily fixable issues. (Redmine issue: #3443)

The original name was unnecessarily long. (Redmine issue: #3443)

The original name was unnecessarily long. (Redmine issue: #3443)

The original name was unnecessarily long. (Redmine issue: #3443)

The original name was unnecessarily long. (Redmine issue: #3443)

The original name was unnecessarily long. (Redmine issue: #3443)

The original name was unnecessarily long. (Redmine issue: #3443)

The original name was unnecessarily long. (Redmine issue: #3443)

The original name was unnecessarily long. (Redmine issue: #3443)

The original name was unnecessarily long. (Redmine issue: #3443)

To be more consistent with the rest of the system this patch moves the built-in index page to separate pluggable module. There is still room for improvement by using Jinja2 macro for rendering breadcrumb navigation. Currently it is used only within part of the system. (Redmine issue: #4220,#3443)

The reporting dashboards now demonstrate new feature: quick search options and time window paging. For performing common quick searches it is now possible to choose the appropriate option from presented list and get results without choosing the time windows manually. Additionally the result page for this quick search option provides means for paging back and forward in time with appropriate time window. For example you may search for current month and then use the time window paging to get results for previous month. (Redmine issue: #4321)

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)

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)

When searching reports by time, the report createtime attribute is now used instead of report time window information. I think, that the moment the event is being reported is more usefull to the user that the time window for which it was generated. (Redmine issue: #4321)

(Redmine issue: #4321)

(Redmine issue: #4321)

Improved working with item action and context anction menus and working with view metadata within the definitions of those menus. (Redmine issue: #4235)

The base implementations for web interface artefacts were redesigned to enable better propagation of view class metadata into the templates, to make the implementation of additional views even more easy and to enable easy development of AJAX backend API services. (Redmine issue: #4366,#4235)

The handle attribute was designed to allow unauthenticated access to reports by knowing the secret token. This however turned out to be redundant, because the report label already contains random component, so it can not be guessed and can therefore be used as access token. (Redmine issue: #4242)

Feature: Added explicit usage of right submenu alignment for all relevant item context action menus.

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)

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)

On busy server the report storage can easily contain hundreds of thousands of files and things can start to get really slow when working with that particular directory. This patch will solve that problem by sorting reports according to the timestamp within the report file name. (Redmine issue: #3378)

(Redmine issue: #3734)

(Redmine issue: #3443)

(Redmine issue: #3443)

(Redmine issue: #3734)

The maintainer permission is now used as slightly less powerfull administrator. Added permission for any role. It is now enforced wherever possible. Added prototype dump of all registered view permissions, however permission enforced by authorize_item_action callback are missing in the list. (Redmine issue: #3734)

This patch introduces huge amount of work related to Hawat web interface. I was just clicking through the interface and trying to improve everything that popped out at the moment. There are following improvements:

* Enabled DataTable localication plugins.
* Implemented common layout for object management views (list views).
* Redesigned application menu implementation.
* Enhanced application menu to support contextual item action menus in listing tables. All administration list views now use it to generate contextual action toolbars.
* Menu object is now used even to generate breadcrumb menus.
* Simplified working with view icons and their propagation into action menus.
* Implemented AJAX spinner and used AJAX to fetch raw report data to web interface. There is stil a lot of room for improvements, the idea is for the user to be able to inteligently browse through the loaded data in some way.
* Redesigned object administration views (users, groups, filters, networks).
* Cleaned up list of built-in icons.
* Improved web interface translations after the changes in this commit.
* Fixed the bug in serving report data files.

(Redmine issue: #3734,#3443)