You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use shared navigation. One user shares a navigation structure with all other users. Since our switch to "icingadb-web" this behaviour occured. With the "monitoring" module, this did not happen.
To Reproduce
Provide a link to a live example, or an unambiguous set of steps to reproduce this issue. Include configuration, logs, etc. to reproduce, if relevant.
Click on an navigation item with sub-entries to expand
the error occures reproduceable
Expected behavior
If you click on a navigation item with sub entries, it expands and on the right side of the ui it souldn't expect a parameter for the right side.
Screenshots
Your Environment
Include as many relevant details about the environment you experienced the problem in.
Icinga DB Web version (System - About): 1.1.2
Icinga Web 2 version (System - About): 2.12.1
Web browser: edge
Icinga 2 version (icinga2 --version): 2.13.9
Icinga DB version (icingadb --version): 1.2.0
PHP version used (php --version):7.2.24
Server operating system and version: rhel8
The text was updated successfully, but these errors were encountered:
Describe the bug
We use shared navigation. One user shares a navigation structure with all other users. Since our switch to "icingadb-web" this behaviour occured. With the "monitoring" module, this did not happen.
To Reproduce
Provide a link to a live example, or an unambiguous set of steps to reproduce this issue. Include configuration, logs, etc. to reproduce, if relevant.
Expected behavior
If you click on a navigation item with sub entries, it expands and on the right side of the ui it souldn't expect a parameter for the right side.
Screenshots
Your Environment
Include as many relevant details about the environment you experienced the problem in.
icinga2 --version
): 2.13.9icingadb --version
): 1.2.0php --version
):7.2.24The text was updated successfully, but these errors were encountered: