Because leapp was not correctly reporting "error" findings in the leapp-report.json file, we've had to recommend customers use --report-schema=1.2.0 option as a way to solve the issue. This workaround was also recently rolled into the infra.leapp community Ansible collection here.
Unfortunately, the Leapp Report UI does not render inhibitor flags or any tags when the report is generated using the new schema. The changes in this PR make it so that the UI renders the report correctly for reports generated using the default schema or the new 1.2.0 version.

https://gitlab.cee.redhat.com/oamg/upgrades-dev/leapp-report-ui/-/merge_requests/21