You need to sign in or sign up before continuing.
Handle MR report widgets differently based on MR status
Problem to solve
Currently, each MR widget is fetched every time the user views a merge request page. This is done regardless if the MR is closed or archived. We could improve performance by not fetching these widgets if the MR is closed or archived. Or if we want still show the widgets when the MR is closed, we can at least hide them for archived MRs.
Intended users
All customers
User experience goal
Have a quicker page loading experience for closed/archived MRs.
Proposal
For many of these, the backend exposes the API endpoints for fetching the reports. We could do a check on the MR for the backend side to not expose those paths if the MR is closed/archived.
What does success look like, and how can we measure that?
The closed/archived MRs no longer show the MR widget reports.