<!--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=365969) </details> <!--IssueSummary end--> ## Problem to Solve The `Assignees` field in merge requests doesn't serve a clear purpose in combination with Reviewers. Is that field supposed to be the author? Is that person(s) supposed to provide an approval? Does that person ultimately merge the MR? In some cases the lack of distinction with reviewers has made it so some teams don't adopt reviewers. ## Proposal We should remove the `Assignees` field from merge requests and replace the field with `Authors`. Authors should be automatically populated by users who `author` or `commit` changes to the merge request. This gives a clear indication of the role those people are playing and leaves reviewers to serve the review functionality of code review. ### Additional Details The Reviewers field in merge requests is where additional functionality related to code review is continuing to be added. Things like: - Suggested Reviewers - Re-Request Review - Approval Indications