<!-- The first section "Release notes" is required if you want to have your release post blog MR auto generated. Currently in BETA, details on the **release post item generator** can be found in the handbook: https://about.gitlab.com/handbook/marketing/blog/release-posts/#release-post-item-generator and this video: https://www.youtube.com/watch?v=rfn9ebgTwKg. The next four sections: "Problem to solve", "Intended users", "User experience goal", and "Proposal", are strongly recommended in your first draft, while the rest of the sections can be filled out during the problem validation or breakdown phase. However, keep in mind that providing complete and relevant information early helps our product team validate the problem and start working on a solution. --> ### Release notes <!-- What is the problem and solution you're proposing? This content sets the overall vision for the feature and serves as the release notes that will populate in various places, including the [release post blog](https://about.gitlab.com/releases/categories/releases/) and [Gitlab project releases](https://gitlab.com/gitlab-org/gitlab/-/releases). " --> For people with more than Gitlab account, it's necessary configuring different Hosts entries in the SSH configuration. This causes that the git URI in the clone dropdownlist, needs to be changed manually. eg: ```bash Host gitlab.com hostname gitlab.com user git IdentityFile ~/.ssh/id_rsa_gitlab_username1 IdentitiesOnly yes Host gitlab.com.user2 hostname gitlab.com IdentityFile ~/.ssh/id_rsa_gitlab_username2 user git IdentitiesOnly yes ``` Then, for the `user2`, you need to copy and edit before executing the clone to something like: `git clone git@gitlab.com.user2:org/folder/repo.git` It would be great to count with a custom additional URI in the dropdown list, customizable from the Profile's settings.  ### Problem to solve <!-- What problem do we solve? Try to define the who/what/why of the opportunity as a user story. For example, "As a (who), I want (what), so I can (why/value)." --> It is more a UX issue, on which it is necessary to change manually a URI that could be customized. ### Intended users <!-- Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later. End users. ### User experience goal <!-- What is the single user experience workflow this problem addresses? For example, "The user should be able to use the UI/API/.gitlab-ci.yml with GitLab to <perform a specific task>" https://about.gitlab.com/handbook/engineering/ux/ux-research-training/user-story-mapping/ --> ### Proposal <!-- How are we going to solve the problem? Try to include the user journey! https://about.gitlab.com/handbook/journeys/#user-journey --> - Option at Profile's settings that allows to add a custom git URI - Then, the custom URI will be used in the "clone repository" dropdown list for adding an additional item. ### Further details <!-- Include use cases, benefits, goals, or any other details that will help us understand the problem better. -->