Design: MR "Reports" tab vision
Problem to solve
See the MVC Issue here
Background & context
Over the past few years, several UX initiatives, including two Key Results (KRs; 1, 2), have been focused on improving the management of security results in the Merge Request (MR). Despite generating valuable ideas for enhancing the code review experience and testing well with users, the proposed solutions from these past initiatives have faced challenges in gaining support from stakeholders due to their perceived complexity of implementation, notable deviation from the existing MR experience, and lack of clear ownership. As a result, the underlying problem persists.
Problem space
The following issues outline some of the primary problems this proposal aims to solve:
- Introduce merge check for merge request approva... (#444459 - closed)
- Re-evaluate report widget information architecture (#444464)
Intended Users
- Engineering teams
Need & Primary JTBD
- JTBD: When I'm making changes, I want to deliver secure and performant code, so I can ensure the integrity of my organization's software is not compromised.
- Need: Product is delivered to end-users, Security and Compliance policies are maintained, and the integrity of the Organization's assets are not compromised.
Goal
Users will be able to assess, in detail, what is blocking or negatively impacting a MR, in one location
Proposal
To be added...