Bug 1391673 - WebUI: Tag visibility - Container Templates should honor tag visibility
Summary: WebUI: Tag visibility - Container Templates should honor tag visibility
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: GA
: 5.8.0
Assignee: zakiva
QA Contact: Dafna Ron
URL:
Whiteboard: ui:tag:container
Depends On: 1421184
Blocks: 1401559
TreeView+ depends on / blocked
 
Reported: 2016-11-03 18:04 UTC by Ramesh A
Modified: 2017-06-12 16:39 UTC (History)
9 users (show)

Fixed In Version: 5.8.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1401559 (view as bug list)
Environment:
Last Closed: 2017-06-12 16:39:23 UTC
Category: ---
Cloudforms Team: Container Management
Target Upstream Version:
Embargoed:
rananda: automate_bug+


Attachments (Terms of Use)

Description Ramesh A 2016-11-03 18:04:16 UTC
Description of problem:
Container Templates should honor tag visibility

Version-Release number of selected component (if applicable):
5.7.0.9-beta2.1.20161101182054_eb0afaa

How reproducible:
Very

Steps to Reproduce:
1. Manage a Container (say openshift)
2. Create a new role
3. Create a new group based out of the above role.  Assign a tag in "My Company Tags" under "Assign Filters" section 
4. Create a user and assign the above role
5. Login as new user and navigate to Compute ==> Container ==> Container Templates

Actual results:
Displays all the available Container Templates

Expected results:
Should honor tag visibility.  Only those builds which are tagged and matching to the user's group tag should get displayed

Additional info:

Comment 2 zakiva 2016-11-20 14:10:34 UTC
Bug fix:
https://github.com/ManageIQ/manageiq/pull/12759

Comment 9 Dafna Ron 2017-02-10 15:02:24 UTC
blocked on 5.8: 

https://bugzilla.redhat.com/show_bug.cgi?id=1421184

Comment 10 Dafna Ron 2017-03-22 14:35:58 UTC
verified on cfme-5.8.0.7-1.el7cf.x86_64


Note You need to log in before you can comment on or make changes to this bug.