(Redmine issue: #4321)

Enabled the 'classes' and 'severities' pie charts for event and report dashboards and report detail. (Redmine issue: #4321)

The IDEA event dashboard and timeline calculations are taking too long. I have attempted to optimize the performance as much as possible without bigger design changes. (Redmine issue: #4321)

Improved the calculations of time step size for timeline charts. Improved the format of rendered time stamp for chart time scale. (Redmine issue: #4321)

(Redmine issue: #3361,#3443)

(Redmine issue: #4321)

(Redmine issue: #1017)

(Redmine issue: #4321)

Each of the sub-statistics like number of events per category, abuse etc. is not rendered in separate timeline chart. (Redmine issue: #4321)

(Redmine issue: #4321)

Because the other pats of code use timezone unaware timestamps implicitly in UTC. (Redmine issue: #4321)

When fetching data from database, the 'event' column is not retrieved, because it is not necessary for instantinating the IdeaGhost event class. (Redmine issue: #4321)

When the time interval is not explicitly set, the minimal detection time value is retrieved from database and used as chart beginning. The current time is used as chart end. This approach enabled us to retrieve the dataset from the database unsorted and it might produce performance boost. (Redmine issue: #4321)

Removed files, that were accidentally copied when creating the pluggable timeline module.

All renderable views now have the ability to create time marks to enable tracing the most expensive operations. First view using this feature is the new timeline search view, because we need the right place to focus our performance optimization. (Redmine issue: #4321)

The improvement is not fetching all table columns for simple row counting operation.

This module attempts to display the events on a timeline to show event distribution over the period of time. This commit contains initial work, which still needs a lot of improvement before production release. It is nevertheless working. (Redmine issue: #4321)

After lots of research I have discovered, that the problem was in flask_principal not getting information about identity change. This was not discovered during testing, because for some reason API token authentication works after previous login/logout of the user. Problem only occurs when accessing the API using curl or similar tool, or without prior user authentication within the browser. I have found a solution in this thread:

https://github.com/mattupstate/flask-principal/issues/22#issuecomment-145897838

This commit should resolve the issue. (Redmine issue: #4463)

(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)