+++ This bug was initially created as a clone of Bug #1868644 +++ Description of problem: In Add trigger form, Git provider type dropdown lists TriggerBindings and ClusterTriggerBindings without resource badges which makes it difficult for the user to distinguish Version-Release number of selected component (if applicable): 4.5,4.6 How reproducible: Always Steps to Reproduce: 1. Create a pipeline 2. click on Add trigger option in the pipeline page actions. Actual results: In Git type provider dropdown, TriggerBindings and ClusterTriggerBindings are shown without any badges. Expected results: The dropdown items should contain the resource badges to differntiate the resource based on the kind.
Created attachment 1724952 [details] Added resource badges in the add trigger form dropdown-1
Created attachment 1724954 [details] Added resource badges in the add trigger form dropdown-2
Verified on build version: 4.5.0-0.ci-2020-10-28-094422 Browser version: chrome 84
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 (OpenShift Container Platform 4.5.17 bug fix update), 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-2020:4325