You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Anthony Penniston (JIRA)" <ji...@apache.org> on 2014/10/10 16:54:33 UTC

[jira] [Updated] (AMBARI-7704) On initially creating custom config, previous default config version is unclickable

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

Anthony Penniston updated AMBARI-7704:
--------------------------------------
    Assignee: vitthal (Suhas) Gogate  (was: Anthony Penniston)

> On initially creating custom config, previous default config version is unclickable
> -----------------------------------------------------------------------------------
>
>                 Key: AMBARI-7704
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7704
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 1.7.0
>            Reporter: Anthony Penniston
>            Assignee: vitthal (Suhas) Gogate
>            Priority: Minor
>              Labels: ambari-web
>
> After creating a custom config group that is based off of the default config, initially the default config version will display in the version list, but is unclickable. However, on subsequently editing and saving the custom config, previous versions are now clickable (which takes the user back to the default config).
> 1. Create a custom config
> 2. Notice the previous version is greyed out and unclickable
> 3. Make changes and save the custom config
> 4. Notice the previous versions are now clickable
> The clickability and navigation to the previous config versions should be consistent (e.g. it appears in most cases, it is clickable, so this should be made the case on first creating the custom config).



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