Merge Requests Widgets - Implementation discussion

(Example taken from Figma)

Objective

This issue aims at promoting a discussion between Designers, Engineers and also Product Managers about how to best approach the implementation of the proposals worked on by our UX team.

Related reading/watching

• Design Walkthrough by @jeldergl: https://www.youtube.com/watch?v=rWD_mMKWfVM
• Figma audit and Exploration https://www.figma.com/file/iztE4TfG4le33QfROEhWaM/UX-OKR-F22Q2-MR-Widget-Audit-and-Exploration?node-id=591%3A2713
• Frontend Docs for MR Widget Extension (available now): https://docs.gitlab.com/ee/development/new_fe_guide/modules/widget_extensions.html

Rough starting point

There is a MR Widget Extension component available that can act as the basis for being extended towards supporting the visual proposals as well as restrict the usage to what's supported by the UX Guidelines.

In Q3 we'll be looking to have each individual group that has MR Widgets adjust them to conform to the guidelines.

Ensuring consistency throughout all widgets is a strong requirement for this effort. Leveraging and extending the extension component can help achieve this. This comes with the challenge of coordinating multiple groups efforts in terms of engineering. Ideas for best coordinating are welcome.

Groups/Stages involved

• groupcode review
• groupcompliance
• groupcomposition analysis
• grouptesting
• ~"group::configure"