Ability to sort MRs by popularity of the issue(s) they close
We can currently sort merge requests by popularity (the number of upvotes they received), but when trying to determine which merge request to merge, review, or finish first, a better indicator of its popularity may be the popularity of the issue(s) the MR is set to close, rather than that of the MR itself, since people are far more likely to upvote a problem they'd like to see resolved or a feature they'd liked to see implemented, than a specific implementation of that fix or feature.
If GitLab supported this natively, it would replace this manually curated list of popular ~Platform ~"Community Contribution" coach will finish MRs: https://docs.google.com/spreadsheets/d/16yx8B0Oio_EWEynVrZFEejX9OYDfTTkzBltpbXhxefU/edit#gid=0
We could decide to sort only by the issue upvotes, or by the sum of upvotes on the MR and any linked issues. To make it clear to the user what we're sorting by, we'd likely want to add an indicator of the issue vote count to the MR row as well. If we display both counts (or always display the sum), I think we can have this new sort option replace the existing "Popularity" option.
@hazelyang What do you think, from a UX perspective?
Design
- The
fire
icon only appears after the issue the MR is set to close has got upvotes from users. - When the
fire
icon is in the hover state, a tooltip with text "Issue upvotes" shows up. - The text in the tooltip of upvotes is just "Upvotes" originally. It will be changed to "Merge request upvotes", so users can understand the difference between "Issue upvotes" and "Merge request upvotes" clearly.
Default state | Hover state |
---|---|