Auto-assign a user to a merge request
Release notes
When a user clicks the "Create merge request" button from within an issue, that user will be automatically assigned to the MR. This will help an already smooth process of creating an issue-linked MR be even smoother. Most users click on the 'Create Merge Request' button because they wish to start working on an issue, so auto-assigning that user as the owner of the MR will save most users a step.
Problem to solve
As a developer about to start working on an issue, I want important but easy-to-forget steps to be handled for me So that I can jump into the code as quickly as possible
Most developers just want to code, and don't want to have to remember that they must set themselves as the owner of an MR after they've created a linked MR from an issue. This is already a fantastically convenient feature, but it falls short of amazing because there's still a fiddly part left to do (the developer must assign themselves) before they start.
Team leaders will appreciate the more reliable data around MR ownership, and developers will have one less step in a process to worry about
Intended users
User experience goal
If done right, this feature will be transparent to users as it will be something that happens implicitly. The UX goal with this is that developers will move the cursor to assign the MR to themselves a few times, notice they're already assigned, smile to themselves, and move on with their day.
In terms of team management, the people in charge of making sure there's a constant flow of work will have a better idea of who is working on what and where they are if they see that MR's are linked, and owned, instead of just linked.
Proposal
When a user clicks Create Merge Request
from an issue they will automatically be assigned to the merge request.
Implementation Notes
- We should NOT implement this with a configurable setting.
- Scope is LIMITED to only
Create Merge Request
button in issues. - A Feature Flag should not be used.
Documentation
- Add all known Documentation Requirements in this section. See https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements
- If this feature requires changing permissions, update the permissions document. See https://docs.gitlab.com/ee/user/permissions.html