Skip to content

Add warning to imports when project creation protection is "No one"

Justin Ho Tuan Duong requested to merge 431566-warn-user-that-migrating-with-default-project-creation-protection-set-to-no-one-will-not into master

What does this MR do and why?

When Default project creation protection is enabled and set to No one at the group or instance level:

  • Group level with the "Roles allowed to create projects" setting. Docs.
  • Instance level with the "Default project creation protection". Docs.

Also disabled the option to "Import with projects" and changes the button + dropdown to only button with "Import without projects".

This is needed because importing projects will fail when project creation protection is "No one".

Changelog: changed

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Before After
Import_with_project_creation_protection_before Import_with_project_creation_protection_after

How to set up and validate locally

Import groups by direct transfer

  1. On the left sidebar, at the top, select Create new... (+) and New group. Then select Import group.
  2. In GitLab source instance base URL, enter your GDK URL. For example, http://127.0.0.1:3000.
  3. Enter Personal access token with a token from your GDK.
  4. Select Connect instance.
  5. You should be on the Import groups by direct transfer page.

Change Default project creation policy on the instance level

  1. Go to Admin Area > Settings > General. For example, http://127.0.0.1:3000/admin/application_settings/general#js-visibility-settings.
  2. Expand the Visibility and access controls section.
  3. Change Default project creation protection to No one and select Save changes.

Change Default project creation policy on the instance level

  1. Go to Group > Settings > General. For example, http://127.0.0.1:3000/groups/flightjs/-/edit#js-permissions-settings.
  2. Expand the Permissions and group features section.
  3. Change Roles allowed to create projects to No one and select Save changes.

Related to #431566 (closed)

Edited by Justin Ho Tuan Duong

Merge request reports