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
Describe the bug
When multiple datapoints are configured it is possible to disable some of them so that they are not shown. At least one datapoint needs to be kept enabled. The problem is when one tries to disable the last datapoint the corresponding alert is not just affecting the current datapoint but all other datapoints. At that point, it is not possible to re-enable the other datapoints and the dashboard has to be reloaded.
To Reproduce
Steps to reproduce the behavior:
Configure three datapoints A, B, C
Disable datapoints A,B
Try to disable datapoint C
Warning is shown for all three datapoints and toggling the status is disabled for all of them.
Expected behavior
Warning should only affect current datapoint. It should be possible to enable another datapoint. The warning on the previous datapoint should go away and it should be possible to disable it now.
Screenshots
Desktop (please complete the following information):
OS: Win 11
Browser Chrome
Version 128.0.6613.113
The text was updated successfully, but these errors were encountered:
Describe the bug
When multiple datapoints are configured it is possible to disable some of them so that they are not shown. At least one datapoint needs to be kept enabled. The problem is when one tries to disable the last datapoint the corresponding alert is not just affecting the current datapoint but all other datapoints. At that point, it is not possible to re-enable the other datapoints and the dashboard has to be reloaded.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Warning should only affect current datapoint. It should be possible to enable another datapoint. The warning on the previous datapoint should go away and it should be possible to disable it now.
Screenshots
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: