Bug 1772591

Summary: [UI] Migrate network role icons to pattern fly 4
Product: [oVirt] ovirt-engine Reporter: Dominik Holler <dholler>
Component: Frontend.WebAdminAssignee: bugs <bugs>
Status: CLOSED DEFERRED QA Contact: Michael Burman <mburman>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: futureCC: bugs, dholler, sgratch
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-09-29 11:33:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dominik Holler 2019-11-14 17:09:31 UTC
Description of problem:
The network role icons should be replaced by their pattern fly 4 pedants.



Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=1477044#c4
(In reply to Laura Wright from comment #4)
> Here is some of the getting started information for icons in PatternFly 4: 
> 
> https://www.patternfly.org/v4/get-started/developers#using-styles
> 
> Here are some of the examples of icons offered in PatternFly 4:
> 
> https://www.patternfly.org/v4/design-guidelines/styles/icons
> 
> 
> If you have more specific questions I can connect you with the PatternFly
> dev team. You can also ask questions on the forum:
> https://forum.patternfly.org/ and join the Slack channel:
> https://patternfly.slack.com/

Comment 2 Michal Skrivanek 2021-08-20 11:01:57 UTC
This bug/RFE is more than a year old and it didn't get enough attention so far, and is now flagged as pending close. 
Please review if it is still relevant and provide additional details/justification/patches if you believe it should get more attention for the next oVirt release.

Comment 3 Michal Skrivanek 2021-09-29 11:33:06 UTC
This bug didn't get any attention in a long time, and it's not planned in foreseeable future. oVirt development team has no plans to work on it.
Please feel free to reopen if you have a plan how to contribute this feature/bug fix.