Created attachment 1106487 [details] Tenant tree with same child tenant names Description of problem: Names of tenants are unique on parent tenant level but can have the same name in child tenants. This might be confusing for end users, because you see the same tenant name several times and you are not able identify which name is which part of tenant/child-tenant tree. See attached screenshot. Version-Release number of selected component (if applicable): 5.5.0.13 How reproducible: always Steps to Reproduce: 1. As super administrator create tenant1 2. Create multiple child tenants tenant1_sub1 under tenant1. It is allowed to use tenant1_sub1 several times in nested tree. 3. Create new parent tenant (Child of My Company tenant) with name tenant1_sub1 4. Navigate to groups, edit existing group and open Project/tenant dropdown list Actual results: When modifying group, there are multiple items with same name in Project/Tenant dropdwon list. See attached screenshot. Expected results: 1. Tenant/Project name is unique in whole CFME UI 2. In Project/tenant dropdown items will be listed as tree (e.g. My Company/tenant1/tenant1_sub1/tenant1_sub1/tenant1_sub1) Additional info:
https://github.com/ManageIQ/manageiq/pull/6122
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/08a4716920e959c901120d7adff20ef9cc533337 commit 08a4716920e959c901120d7adff20ef9cc533337 Author: Milan Zazrivec <mzazrivec> AuthorDate: Mon Jan 11 14:23:33 2016 +0100 Commit: Milan Zazrivec <mzazrivec> CommitDate: Mon Jan 18 20:22:15 2016 +0100 Add all tenant ancestors to group creation page This is to avoid ambiguity in case there are more tenants with the same name. https://bugzilla.redhat.com/show_bug.cgi?id=1292165 app/controllers/ops_controller/ops_rbac.rb | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-)
https://github.com/ManageIQ/manageiq/pull/6191
Detected commit referencing this ticket while ticket status is MODIFIED.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1348