Jump between my discussions in a merge request
### Problem to solve When I return to a merge request that I have already reviewed, it is hard to find the discussions that I have participated in to review new comments by others. I have to search the whole page by name using the browser search feature. I want to be able to jump from the discussion I am in, to the start of the next discussion that I have participated in so that I can quickly navigate the discussions that I am participating in and ignore the rest. ### Further details <!-- Include use cases, benefits, and/or goals (contributes to our vision?) --> ### Proposal - Allow the discussions on the merge request diff to be filtered by the reviewer who left the feedback - Clicking on a reviewer in the merge widget should take you to the diff view with discussions filtered by reviewer | **Mockup:** reviewers | **Mockup:** filter diff discussions | | --- | --- | | ![Artboard_20190313_105810](/uploads/7f16dba4d6ed3445f85906ac4660274c/Artboard_20190313_105810.png) | ![Artboard_20190320_124222](/uploads/81f68a775deef2420745f57ce495ae3f/Artboard_20190320_124222.png) | ### Permissions and Security <!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)? --> ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> ### Links / references
issue