[
https://issues.apache.org/jira/browse/AMBARI-21715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16149166#comment-16149166
]
Hadoop QA commented on AMBARI-21715:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12884691/AMBARI-21715_trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12127//console
This message is automatically generated.
> Upgrade History Is too Verbose
> ------------------------------
>
> Key: AMBARI-21715
> URL: https://issues.apache.org/jira/browse/AMBARI-21715
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.5.3
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Fix For: 2.5.3
>
> Attachments: AMBARI-21715.patch, AMBARI-21715_trunk.patch,
> BUG-85441.gif, Screen Shot 2017-08-03 at 4.30.46 PM.png
>
>
> It looks like the Upgrade History page is displaying a row for every service
> in a particular upgrade. I had thought we had mockups which kept the upgrade
> history to a single row-per-upgrade and when you clicked on the that upgrade,
> you were told more information about it (such as the to/from per-service).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
