Highlight that an action is required of you in a merge request when it passes a time threshold
<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=505414) </details> <!--IssueSummary end--> ## Proposal We all busy, so having a gentle reminder that there is an action waiting on us could help us take action so that we can unblock the people with collaborate with. Inspired by an email related feature [mentioned here](https://gitlab.com/gitlab-org/gitlab/-/issues/497573#note_2155092198) and concept of action status https://gitlab.com/gitlab-org/gitlab/-/issues/504685#note_2216254545, the idea is to highlight an action that is required of you in the list of merge requests in "Your work > Merge requests". The reminder should be clickable and take the user to the most relevant spot in the merge request to take the action. By default it would link to the merge request page. ![CleanShot_2024-11-20_at_13.24.44](/uploads/18e7fc938908fc963b205ae0bc52bd59/CleanShot_2024-11-20_at_13.24.44.png) Relates to https://gitlab.com/gitlab-org/gitlab/-/issues/459898+ ### Question 1. What is a reasonable time frame before invoking a reminder? The introduction of this time value might be something that would be custom to each team. Fast/small MRs with quick turnaround times - this could be hours. Larger changes - days. What is a reasonable default? ### Actions based on job performer - `Code reviewer` that action could be "start review". - `Code author` that action could be resolving discussions, reassigning reviewers, etc - "_Because sometimes the review takes too long because reviewer is busy or went on holiday and you might need to reassign._" https://gitlab.com/gitlab-org/gitlab/-/issues/497573#note_2152013402 ### Related work in the industry - [Nudge: Accelerating Overdue Pull Requests Towards Completion [MS]](https://arxiv.org/pdf/2011.12468) - [Using Nudges to Accelerate Code Reviews at Scale [META]](https://users.encs.concordia.ca/~pcr/paper/NudgeBot2022FSE-preprint.pdf)
issue