<!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> ## Problem to solve In merge requests, as I review files, review discussions, and more changes/discussions are added, it's very difficult to keep track of what you have reviewed in the past and what still needs to be reviewed. Equally as important to tracking these or your own review, is being able to communicate the progress of your review to other stakeholders who might be tracking the status of the merge request. ### Further details **Crucible** does a nice job of tracking exactly which revisions, which files and which comments have been seen. ## Proposal The current scope of tracking is limited to tracking files that are reviewed as part of the merge request review process. - [x] Mark files as viewed - [ ] Sync viewed file status for users - [ ] Display viewed files per reviewer ### Current Status | Date | Feature | Status | | ------ | ------ | ------- | | 2021-02-22 | [Mark file as viewed](https://gitlab.com/gitlab-org/gitlab/-/issues/17531) | Released in GitLab 13.9, users can mark files as viewed when reviewing a merge request. This information is not stored or shared with other users | ### Interested customers * https://gitlab.my.salesforce.com/00161000004bZPD * https://gitlab.my.salesforce.com/0014M00001lZtL9 * https://gitlab.my.salesforce.com/0016100001E1liJ * https://gitlab.my.salesforce.com/0016100001F2Gsw * https://gitlab.my.salesforce.com/0064M00000WtcW2