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

Velmurugan Periasamy updated RANGER-799:
----------------------------------------
    Attachment:     (was: RANGER-799.patch)

> Ranger UI fixes - partial search not working on Policy listing page
> -------------------------------------------------------------------
>
>                 Key: RANGER-799
>                 URL: https://issues.apache.org/jira/browse/RANGER-799
>             Project: Ranger
>          Issue Type: Bug
>          Components: admin
>    Affects Versions: 0.5.0, 0.6.0
>            Reporter: Gautam Borad
>            Assignee: Gautam Borad
>             Fix For: 0.6.0
>
>         Attachments: 0001-RANGER-799-UI-fixes-partial-policy-search.patch
>
>
> *List of UI issues* 
> 1. (Policy) Partial search not working. Consider the following 3 policies:
>   * test_hdfs-1-20151214074249
>   * test1
>   * test_policy
> Now on search for policy name as "test" no results are shown. Instead a 
> message is shown: "No policies found".
> 2. (Policy) While disabling audit logging for a policy, user has to add at 
> least one group in that policy. If not, a message is displayed: "You must 
> have at least one or more user/group access defined for the policy." Also in 
> that policy even if users are already listed then too the same message comes 
> for group.
> 3. (Audit > Admin) Audit log of Service Update shows incorrect values. Try 
> updating some fields of any service and check the Audit logs.
> 4. (Profile page) If Last name is mandatory then message shown should be 
> proper, currently the message shown is "Please try different name".
> 5. (Users/groups) From admin login, we need to remove search by role 
> "keyadmin" from list as admin is not able to see users with "keyadmin" role. 
> If keyadmin has Users/Groups tab permission then should it not be able to 
> search by role as "admin". If user has Users/Groups tab permission then it 
> should show User and Admin role.



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

Reply via email to