Configure default assignee for issues
Summary
It would be nice if we could configure a default assignee at the project and group levels.
Activity
@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.)
Edited by username-removed-393947mentioned in issue #21365 (closed)
@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.
Edited by 🚄 Job van der Voort 🚀@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 #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):
- All project members
- Select project members
- Use the same search field from
/GROUP_NAME/PROJECT_NAME/project_members, which searches against the list of project members
- Use the same search field from
@JobV please let me know your thoughts.
Edited by username-removed-393947- Go to
/cc @victorwu
added feature proposal label
marked this issue as related to #3126 (moved)
marked this issue as related to #37722
moved to gitlab#5386
Hey!
👋 GitLab is moving all development for both GitLab Community Edition and Enterprise Edition into a single codebase. The current
gitlab-cerepository will become a read-only mirror, without any proprietary code. All development is moved to the currentgitlab-eerepository, which we will rename to justgitlabin the coming weeks. As part of this migration, issues will be moved to the currentgitlab-eeproject.If you have any questions about all of this, please ask them in our dedicated FAQ issue.
https://gitlab.com/gitlab-org/gitlab-ee/issues/13855You can also find more information here:
https://gitlab.com/gitlab-org/gitlab-ee/issues/13304- https://about.gitlab.com/2019/08/23/a-single-codebase-for-gitlab-community-and-enterprise-edition/
Frequently Asked Questions
For an up to date list of questions and answers, please take a look at
https://gitlab.com/gitlab-org/gitlab-ee/issues/13855What will we do with the repository names?
https://gitlab.com/gitlab-org/gitlab-ee/ will become https://gitlab.com/gitlab-org/gitlab, and https://gitlab.com/gitlab-org/gitlab-ce will become https://gitlab.com/gitlab-org/gitlab-foss.
Why rename gitlab-ce to gitlab-foss?
Using "gitlab" and "gitlab-ce" would be confusing, so we decided to rename gitlab-ce to gitlab-foss to make the purpose of this FOSS repository more clear
I created a merge requests for CE, and this got closed. What do I need to do?
You will need to create a merge request at https://gitlab.com/gitlab-org/gitlab-ee/. This link will eventually redirect to https://gitlab.com/gitlab-org/gitlab.
How does the licensing work in this new setup?
Everything in the
ee/directory is proprietary. Everything else is free and open source software. If your merge request does not change anything in theee/directory, the process of contributing changes is the same as when using the gitlab-ce repository.Will you accept merge requests on the gitlab-ce/gitlab-foss project after it has been renamed?
No. Merge requests submitted to this project will be closed automatically.
Will I still be able to view old issues and merge requests in gitlab-ce/gitlab-foss?
Yes.
How will this affect users of GitLab CE using Omnibus?
No changes will be necessary, as the packages built remain the same.
How will this affect users of GitLab CE that build from source?
Once the project has been renamed, you will need to change your Git remotes to use this new URL. GitLab will take care of redirecting Git operations so there is no hard deadline, but we recommend doing this as soon as the projects have been renamed.
Where can I see a timeline of the remaining steps?
https://gitlab.com/gitlab-org/gitlab-ee/issues/13304Will community contributions submitted to the new "gitlab" repository be available in the new gitlab-foss repository?
Yes, these changes will be synced to gitlab-foss automatically, several times per day.
