[
https://issues.apache.org/jira/browse/AMBARI-19052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15712972#comment-15712972
]
Hudson commented on AMBARI-19052:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-branch-2.5 #433 (See
[https://builds.apache.org/job/Ambari-branch-2.5/433/])
AMBARI-19052. Re-arrange "Role Based Access Control" info table (akovalenko:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ab3d72914254b9ee13708cb8a5987d0a2c4459a9])
* (edit)
ambari-admin/src/main/resources/ui/admin-web/app/views/modals/RoleDetailsModal.html
* (edit)
ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/RoleDetailsModal.js
* (edit)
ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/Cluster.js
> Re-arrange "Role Based Access Control" info table
> -------------------------------------------------
>
> Key: AMBARI-19052
> URL: https://issues.apache.org/jira/browse/AMBARI-19052
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.4.0
> Reporter: Aleksandr Kovalenko
> Assignee: Aleksandr Kovalenko
> Fix For: 2.5.0
>
> Attachments: AMBARI-19052.patch
>
>
> The RBAC info table should be organized so that the permissions flow down
> like below:
> ||Permissions||Role 1||Role 2||Role 3||
> |Perm 1|(/)|(/)|(/)|
> |Perm 2| |(/)|(/)|
> |Perm 3| | |(/)|
> We have areas in the table where it doesn't look like that, for example "View
> service operational logs" should be right after "Manage configuration groups".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
