ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-7111) Configs: compare against current should not have cancel/save
Date Tue, 02 Sep 2014 14:12:21 GMT

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

Hudson commented on AMBARI-7111:
--------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #103 (See [https://builds.apache.org/job/Ambari-trunk-Commit/103/])
AMBARI-7111 Configs: compare against current should not have cancel/save.  (ababiichuk) (ababiichuk:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=9571ac8d530ee9faff884ff72bc5578911f4e104)
* ambari-web/app/templates/common/configs/config_history_flow.hbs


> Configs: compare against current should not have cancel/save
> ------------------------------------------------------------
>
>                 Key: AMBARI-7111
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7111
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 1.7.0
>            Reporter: Andrii Babiichuk
>            Assignee: Andrii Babiichuk
>             Fix For: 1.7.0
>
>         Attachments: AMBARI-7111.patch
>
>
> when compare old version with old or current (save/discard) is present but config textareas
are disabled and we can't edit them - so (save/discard) shouldn't be present



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message