[ 
https://issues.apache.org/jira/browse/AMBARI-20254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15901908#comment-15901908
 ] 

Hudson commented on AMBARI-20254:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6979 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/6979/])
AMBARI-20254. Service Alert Popup - Unexpected User Experience. (Vivek (yusaku: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=66c94e9937343be0c1db9f51fad22556c18fb77e])
* (edit) ambari-web/app/styles/alerts.less
* (edit) ambari-web/app/templates/main/service/info/service_alert_popup.hbs
* (edit) ambari-web/app/models/alerts/alert_definition.js
* (edit) ambari-web/app/controllers/main/service/info/summary.js


> Service Alert Popup - Unexpected User Experience
> ------------------------------------------------
>
>                 Key: AMBARI-20254
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20254
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.5.0
>            Reporter: Vivek Ratnavel Subramanian
>            Assignee: Vivek Ratnavel Subramanian
>            Priority: Critical
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-20254.v0.branch-2.5.patch, 
> AMBARI-20254.v0.trunk.patch, AMBARI-20254.v1.branch-2.5.patch, tooltip2.png
>
>
> AMBARI-19049 introduced some UI changes that causes regression in UX for the 
> Service Alert popup.
> With the change, the user has to click on the expander to see any alert 
> context. And the expander UX is strange too. Clicking anywhere (including the 
> hyperlinked text as well as the background) in the header takes the user to 
> the alerts page. This is not the experience the user would expect based on 
> conventions.
> The cases in which too much context is displayed and therefore needs special 
> handling is not the norm, so crippling UX for the special case is not the way 
> to go.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to