Add supervisor/client/sponsor to issue
When using GitLab as a project management tool (mainly the issues including the board), assigning one or more GitLab user(s) is the way of telling who's responsible to solve a specific issue. Unfortunately quite often the person responsible to solve an issue isn't the one allowed to decide if how the issue was addressed is sufficient. So there should be a way to allow moving issues thought the hands of different people (assignees) but keep one user who's still in charge in the end. For code we can address this somehow by using protected branches but that doesn't work if no code is involved but only issues instead.
- John is the head of marketing and decides, that a new company presentation must be created.
- John asks his assistant Paul to create an issue with the requirements he has regarding the presentation.
- After Paul has created the issue, he assigns Claire to the issue who's a copywriter.
- Claire structures the presentation body and writes all the necessary text elements.
- Claire hands over the issue to Sarah (by assigning her) who's a graphics designer.
- Sarah makes the presentation look fancy and stylish.
At this point the presentation is complete based on the opinion of Claire and Sarah but they aren't the supervisor/client/sponsor so they are not in the position of deciding if this is the way the company presents itself to the world. The person that would be needed to do this is John but neither Claire nor Sarah know that because the issue only indicates that Paul has created the task and he might not remember that this specific task came from John.
So my feature proposal would allow Peter to indicate that John is the one in charge right when creating the issue and this would never had to be changed during the whole process.
I'd recommend to have not only assignees for an issue but in addition the possibility for a supervisor/client/sponsor or however we'd like to call it. By default, the user creating the issue should be pre-selected for this role.