You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Andrii Tkach (JIRA)" <ji...@apache.org> on 2015/11/11 17:53:10 UTC

[jira] [Commented] (AMBARI-13839) Config History: Filter applied after refresh

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

Andrii Tkach commented on AMBARI-13839:
---------------------------------------

10169 tests complete (13 seconds)
  104 tests pending

> Config History: Filter applied after refresh
> --------------------------------------------
>
>                 Key: AMBARI-13839
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13839
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.1.3
>            Reporter: Andrii Tkach
>            Assignee: Andrii Tkach
>            Priority: Critical
>             Fix For: 2.1.3
>
>         Attachments: AMBARI-13839.patch, aftre_refresh.PNG, before_filter.PNG, filter_applied.PNG
>
>
> *Steps to reproduce:*
> # Go to Config History page
> # Apply any filter
> # Refresh page
> *Actual Result:*
> Content filtered by applied filter, but UI has no active filter  



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