[
https://issues.apache.org/jira/browse/AMBARI-11444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587035#comment-14587035
]
Xi Wang commented on AMBARI-11444:
----------------------------------
After applying the second patch, tested e2e for multiple situations about the
thresholds. Worked better.
6567 tests complete (12 seconds)
86 tests pending
> Number Widgets: Empty threshold for 'Critical' still shows the value as
> Critical
> --------------------------------------------------------------------------------
>
> Key: AMBARI-11444
> URL: https://issues.apache.org/jira/browse/AMBARI-11444
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.1.0.
> Reporter: Xi Wang
> Assignee: Xi Wang
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-11444.patch
>
>
> This jira is to understand the expected behavior in the following case:
> Edit a number widget. Current value is 291 (critical). Edit the thresholds so
> that Warning is at 290 and leave critical to empty. The Preview still shows
> it as critical(red).
> From that configuration, as we understand once the value hits 290, it should
> be a warning until it hits the value present in the critical field. as
> critical is empty everything above 290 should be warning.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
