[dev.icinga.com #10877] Store menu entries in database instead of local files

[icinga-migration]

This issue has been migrated from Redmine: https://dev.icinga.com/issues/10877

Created by dgoetz on 2015-12-17 09:51:43 +00:00

Assignee: (none)
Status: New
Target Version: Backlog
Last Update: 2016-04-10 22:09:23 +00:00 (in Redmine)

---

At the moment setting Icinga Web 2 to store user preferences into the database only stores those preferences. I think also storing custom menu entries and dashboards would be useful, but of course will need additional work for the sharing feature.

---

Relations:

• relates #10877

[icinga-migration]

Updated by elippmann on 2016-01-05 10:29:39 +00:00

• Category set to Configuration
• Priority changed from Normal to Low
• Target Version set to Backlog

[icinga-migration]

Updated by elippmann on 2016-04-10 22:08:11 +00:00

• Subject changed from Store menu entries and dashboards in the database if preferences are stored there to Store menu entries in the database

[icinga-migration]

Updated by elippmann on 2016-04-10 22:09:23 +00:00

• Subject changed from Store menu entries in the database to Store menu entries in database instead of local files

[icinga-migration]

Updated by elippmann on 2016-04-10 22:09:42 +00:00

• Relates set to 9371

[nilmerg]

We should avoid making the same mistake: #2129 (Items from modules should be prefixed with <module-name>/)