Improve policy violation description on merge request overview

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Proposal

A customer shared the feedback to improve policy violation description as below:

When there is an issue collecting the reports to evaluate the policy, the user is told that approvals are required, but not the reason approval is required

This information is however visible in GraphQL API, and if visible on the UI would ease customer resolution.

This issue is to discuss adding such information to the UI.

More information and screenshots with examples in the internal ticket.