Follow up "Approval and WIP MR visualization could be confusing #36487" Design + exploration
Per @sarrahvesselov , deliverable for 10.7 here is only UX design. This is not for code implementation in 10.7.
The merge request widget supports multiple work flows by nature. However the problem is that as a user there is no clear way to interpret this in order to quickly digest the information you are interested in.
Currently the merge request widget handles all workflows equally (as there is no way of knowing which workflow a user may be interested in), so none stand out. This isn't the complete problem, but it creates a bland pile of information which is not very accessible.
The workflows mentioned are:
- Status of Code (or Status of CI, or Status of Pipeline, Code Quality)
- Status of Review (Approvals, unresolved discussions)
- Merge button (+ reasons it can't be merged)
- Status of Shipment (staging/production deploy, including metrics)
Make it so anyone following one of those flows has only one place to look. Yes, the other statuses will be competing, but at least their reasons are clear, so you can quickly determine which to focus on and which to ignore. Memory will make this even better.
- Create distinct hubs of information
- Think of uniquely branding each hub/service/test
- Introduce a clear hierarchy system
- Better consistent button locations
- This can greatly help mobile viewports as well
- Overall status of the MR widget should be available at a glance, similar as spotting where a problem is if there is one (Status icons should indicate status in general terms, not be tied to a certain test/ci services)
A wireframe here to illustrate the above points:
This issue should introduce an improved merge request widget design system, which is easily expandable due to correct packaging of already existing information. No new features should be introduced, rather a restructuring of existing data and UI.
|Collapsed view||Expanded view|