Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Wed, 17 Dec 2014 00:39:13 +0000 (UTC)
From: "Richard Zang (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12762152.1418776738000.39678.1418776753478@Atlassian.JIRA>
In-Reply-To: <JIRA.12762152.1418776738000@Atlassian.JIRA>
References: <JIRA.12762152.1418776738000@Atlassian.JIRA>
 <JIRA.12762152.1418776738359@arcas>
Subject: [jira] [Assigned] (AMBARI-8744) Admin View: Create Repo version
 form changes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AMBARI-8744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard Zang reassigned AMBARI-8744:
------------------------------------

    Assignee: Richard Zang

> Admin View: Create Repo version form changes
> --------------------------------------------
>
>                 Key: AMBARI-8744
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8744
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-admin
>    Affects Versions: 2.0.0
>            Reporter: Richard Zang
>            Assignee: Richard Zang
>             Fix For: 2.0.0
>
>
> 1. The stack pulldown that appears should only show HDP-2.2 has it is the only version that has an upgrade pack.
> 2. Perhaps right-align the content of the pulldown (HDP-2.2) so that there isn't so much space from the dot. 
> 3. Add client-side validation for the version.  During testing, it seems that we have to enter all of "x.y-z", so let's validate based on this rule, where x.y-z are numbers.
> 4. (Nice to have) add client-side validation to make sure at least one OS is selected.


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