(Redmine issue: #3387)

(Redmine issue: #3387)

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

(Redmine issue: #3361)

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

Note: This commit was actually created by Jan Mach, but contains the work of Radko Krkoš, who should get all the credit for coming up with the upgrade procedure checklist. (Redmine issue: #4382)

(Redmine issue: #3387)

Since the get parameters are part of the URL, they might end up being stored in insecure locations like web server log files. (Redmine issue: #4366)

(Redmine issue: #4366)

There is an endpoint /api/events/dashboard, that provides JSON document containing overall IDEA message statistics. The data is the same as with the /events/dashboard view. (Redmine issue: #4366)

(Redmine issue: #3387)

There is an endpoint /api/events/metadata, that provides JSON document containing all possible and valid values for various IDEA message attributes like category, severity etc. These can be then used for example for rendering various UI widgets using JavaScript. (Redmine issue: #4366)

(Redmine issue: #3361)

There is the /api/events/<item_id>/show endpoint now, that can be used to retrieve given IDEA message. (Redmine issue: #4366)

Fixing this issue for good will need more thorough thinking and more time, reverting back to previous state for now. (Redmine issue: #4369)

There is a new endpoint at /api/events/search, which provides the same functionality as the HTML search form at /events/search, but it returns a JSON document instead of HTML page. The API is thoroughly described in the documentation of Hawat events pluggable module. (Redmine issue: #4366)

The datetimepicker widgets need special handling when being enabled/disabled. (Redmine issue: #4369)

Previously the API key was visible to anyone with read access to the account. This was obviously a bug, so now it is visible only to the owner of that particular account. (Redmine issue: #4366)

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)

This additional adjustment also discards the hour information, so it adjusts the default timestamps to the whole days. (Redmine issue: #4233)

This new blueprint provides users (admins) with the ability to generate API access keys and use them to access the website. Currently the key generation is restricted only to the administrators, because this feature is considered to be experimental. (Redmine issue: #4366)

(Redmine issue: #3361)

Implementation of certain blueprints might need access to instances of Flask extension/plugin objects, like Babel, LoginManager, Principal etc. (Redmine issue: #4366)

(Redmine issue: #3361)

Started precaching cesnet_inspectionerrors column from events table, replaced text widget with select in event search form.

(Redmine issue: #4350)

(Redmine issue: #4242)

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)

(Redmine issue: #4363)

* All changelogs everywhere are now generated using single Jinja2 macro.
* Redesigned the style of changelog record.
* Group, filter, network and setting changelogs are now accessible to the group managers.
* User changelogs and actionlogs are now visible to the users themselves.
* Translated all newly implemented features into the czech language.

(Redmine issue: #3203)