<!--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=392997) </details> <!--IssueSummary end--> <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> Created on behalf of a ~"GitLab Premium" ~customer [Zendesk ticket](https://gitlab.zendesk.com/agent/tickets/361246)(internal). ### Problem to solve When creating a merge request discussion, whether a single or multi-line comment, it will display up to 15 lines above the intended target diff lines. Depending on the use case, the extra lines may not be relevant and remove focus from the intended selection. ### Proposal <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> Allow the number of lines to be customizable at some level(Instance/Group/Project/Creator). Related code: [`truncated_diff_lines`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/app/models/concerns/discussion_on_diff.rb#L38-59) <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> ### Example project https://gitlab.com/gitlab-gold/jiocastillo/rust-test/-/merge_requests/2 <!-- Label reminders Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->