Description of problem: In 'Edit Role' popup, checkbox of the components (System, Data Center, etc.) is not checked even if there are allowed actions. This may be by design but I think it may be confusing. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Click 'Configure' from top menu 2. Select a role and edit it Actual results: Check boxes are not checked even if there are allowed actions Expected results: Check box to be checked where there is at least one allowed action Additional info:
Flagging as infra for initial research, as they are the subject matter owners. Ala - can you please add a screenshot of a collapsed and non-collapsed tree to highlight what you mean?
Created attachment 1027234 [details] Collapsed view of the components Collapsed view of the components. Look at 'System' component that is not checked. In other attached file, we see that 'LOGIN' and 'AUDIT_LOG_MANAGEMENT' actions are allowed.
Created attachment 1027235 [details] Expanded view of 'System' component
I agree it is indeed confusing. Einav - I talked to Alona and she said that usually it is common to show a "check" sign if all is selected, a white cell if nothing is selected, and a colored cell if things are partially selected. Do we have some infrastructure for that? Shall I open a RFE for that infrastructure?
(In reply to Oved Ourfali from comment #4) > I agree it is indeed confusing. > Einav - I talked to Alona and she said that usually it is common to show a > "check" sign if all is selected, a white cell if nothing is selected, and a > colored cell if things are partially selected. > > Do we have some infrastructure for that? no. > Shall I open a RFE for that infrastructure? no need, we already have bug 985637, bug 999783 to track the lack of 'half-checked' check-boxes throughout the GUI, no need to open another one. moving this BZ to be 'ux'. no need for the UserExperience keyword, it is a simple gap in the GUI current capabilities.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
stale bug without any update for a long time, closing. If you deeply care about it please reopen