Configure default assignee for issues

Summary

It would be nice if we could configure a default assignee at the project and group levels.

feature proposal in GitLab FOSS

Is this on anyones radar? It seems even more important now with the new issue board/features... It's a blocker for us to buy in

@shnhrrsn DIY is probably the best approach since it hasn't already gotten attention, so a MR would help move this along.

Maybe what would help is if we more deeply laid out some ideas on how to implement this (API, UI, etc.)

mentioned in issue gitlab-foss#21365 (closed)

Added ~14281 label

@dandunckelman how would it work? Just a single person? Or multiple / round-robin style?

cc @stanhu @connorshea @DouweM @markglenfletcher as an idea for solving our massive issue influx.

JIRA handles this by having a "Default Assignee" for each Group (falling back to the Group Owner).

By default, Projects use the Group's "Default Assignee", but optionally, a different team member can be selected as the default on a per project basis.

As a first pass, we could consider just having a single assignee, but I think that would be too much for GitLab CE issues alone. Do we want to consider labels when assigning owners?

@JobV Reminds me of https://gitlab.com/gitlab-org/gitlab-ce/issues/18078

@JobV I'd like to see the simplest approach implemented where we can designate a single user as the "default assignee" for a project (maybe make the setting configurable at the group-level later). Here's some detail on how I'd try answering your question:

how would it work?

Setup a Group's Default Assignee (DA)

• Go to /groups/GROUP_NAME/edit
• Present a drop-down menu of the group's members
  • This list only contains group-level members and not users that are members of 1 or more projects in the group.
• Click the drop-down and pick a user to be the DA
• Click Save changes
• From then on, when creating new issues on any project in the group, the issue's assignee will be the DA

Setup a Project's Default Assignee (DA)

• Go to /GROUP_NAME/PROJECT_NAME/edit
• Present a drop-down menu of the project's members
  • Maybe we should show the "group-level DA" and make this setting act as an "override"
• Click the drop-down and pick a user to be the DA
• Click Save changes
• From then on, when creating new issues, the issue's assignee will be the DA

Notes

• Like normal, when the user creating the issue has an access level greater than "guest", they can override the assignee.
• If a "round-robin" approach is established (as discussed in gitlab-foss#18078 (moved)), then I think configuring the DA setting could start as a radio button:
  • Single user - Then present the drop-down menu of members
  • Pool of users - Then present these options for configuring the pool (radio button):
    1. All project members
    2. Select project members
       • Use the same search field from /GROUP_NAME/PROJECT_NAME/project_members, which searches against the list of project members

@JobV please let me know your thoughts.

Added ~874211 label

/cc @victorwu

added feature proposal in GitLab FOSS label

marked this issue as related to gitlab-foss#3126 (moved)

marked this issue as related to gitlab-foss#37722

Would using quick actions and templates solve this? For instance, the template could end with:

/assign @smcgivern

moved from gitlab-foss#19570 (moved)