Bug 1545942
Summary: | [RFE] Ability to set default filters for all users to not show archived VM's | ||
---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Tuan <tuado> |
Component: | UI - OPS | Assignee: | Robin Knaur <rknaur> |
Status: | CLOSED ERRATA | QA Contact: | Sudhir Mallamprabhakara <smallamp> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.8.0 | CC: | bwoolf, hkataria, jfrey, jocarter, lavenel, mfeifer, mpovolny, mshriver, obarenbo, rovalent, simaishi |
Target Milestone: | GA | Keywords: | FutureFeature, RFE |
Target Release: | 5.11.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 5.11.0.15 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-12-12 13:33:48 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | Feature | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | CFME Core | Target Upstream Version: | |
Embargoed: |
Comment 3
Jason Frey
2019-01-31 15:44:11 UTC
(In reply to Jason Frey from comment #3) > This sounds more like an RBAC enhancement to have a permission to see/not > see Archived VMs and the associated entry in the explorer tree. Yes, ROLE should allow to set visibility for VMS, Archived, Retired, Orphans New commit detected on ManageIQ/manageiq-ui-classic/master: https://github.com/ManageIQ/manageiq-ui-classic/commit/ce51bd6944760d0997d514c7caade76ce36a1573 commit ce51bd6944760d0997d514c7caade76ce36a1573 Author: PanSpagetka <rknaur> AuthorDate: Wed Mar 20 06:16:05 2019 -0400 Commit: PanSpagetka <rknaur> CommitDate: Wed Mar 20 06:16:05 2019 -0400 Add scopes for filtering Archived/Orphaned VMs based on RBAC https://bugzilla.redhat.com/show_bug.cgi?id=1545942 app/controllers/vm_common.rb | 2 + 1 file changed, 2 insertions(+) Verified with 5.11.0.17. 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-2019:4199 |