Each group has an attribute indicating self-management. When enabled, notice about group membership requests is sent to all group managers. (Redmine issue: #5832)

Group managers must have the ability to reject unwanted group membership requests. (Redmine issue: #5832)

Reference to non existent vaiable.

(Redmine issue: #3387)

(Redmine issue: #3387)

(Redmine issue: #3361)

(Redmine issue: #3361)

(Redmine issue: #5762)

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: #5278,#5341)

(Redmine issue: #3387,#5062)

Implemented prototype built-in help pages for events/sear4ch and events/show endpoints. Improved the help pluggable module to autodiscover help pages. Improved autogenerated Sphinx documentation for events pluggable module. (Redmine issue: #3361)

(Redmine issue: #4277)

When retrieving for example members of a group list of users was in no particular order. I have fixed that now for all objects where it was relevant.

(Redmine issue: #3443)

(Redmine issue: #4277)

Sometimes the downtime due to the upgrade or error can be noticable to the users, so the well behaving application should have some kind of maintenance mode to inform the users. This commit contains simple web page with capabilites of variable substitutions (to insert separately generated timestamps about the duration of the downtime), an example site configuration for Apache web server and updated documentation page about sustem upgrade. (Redmine issue: #4277)

More details about this improvement are in related Redmine issue. In short summary the idea is to improve performance of searching events by addresses by adding dedicated aggregated IP range columns and use these to narrow the search data. (Redmine issue: #4277)

(Redmine issue: #4518)

(Redmine issue: #4518)

(Redmine issue: #4518)

(Redmine issue: #3387,#5065)

(Redmine issue: #5538)

(Redmine issue: #3387)

HTML snippet rendering library is now more configurable to enable developers customize what will be rendered in what circumstances. (Redmine issue: #5341)

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

* This complements ed74734f where
  the RetryingQuery was introduced to make SQLAlchemy to retry the
  intended operation on DB failure. This should be asserted in a few
  more places to be actually used all the time.

(Redmine issue: #4569)

Additional object data services are now capable of rendering HTML snippets in multiple formats. It now possible to request either simple labels with popover, or full result. (Redmine issue: #5341)

In *events* pluggable module.

Added option to use api_token parameter to supply API key, improved documentation of all authentication service pluggable modules.

It was not always clear what to enter to various event search form fields. This patch attempts to provide help messages to some of the event search form fields.

Users will now be aware, that there are more functions available to them after login.

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: #5341)