Skip to content

Update warning and error messages when project limit is hit

Peter Hegman requested to merge 367020-confusing-behaviour-when-user-project-limit-is-reached into master

What does this MR do and why?

Related to #367020 (closed)

In the admin area you can set a project limit. See https://docs.gitlab.com/ee/administration/settings/account_and_limit_settings.html#default-projects-limit for more information.

When the project limit is reached set we display a warning and an error message if you try and to create a new personal project. Those warnings and errors were a bit confusing so this MR updates the copy to try and be more clear.

Screenshots or screen recordings

Warning on all projects dashboard

warning is no longer shown on this page

Before After
Screenshot_2023-11-01_at_10.39.55_AM Screenshot_2023-11-01_at_10.32.59_AM

Warning on personal projects dashboard

Before After
Screenshot_2023-11-01_at_10.40.15_AM Screenshot_2023-11-01_at_10.33.12_AM

Error when limit is set > 0

Before After
Screenshot_2023-11-01_at_10.42.42_AM Screenshot_2023-11-01_at_10.33.53_AM

Error when limit is 0

Before After
Screenshot_2023-11-01_at_10.43.59_AM Screenshot_2023-11-06_at_11.11.58_AM

How to set up and validate locally

  1. Sign in as an admin
  2. Find a user in /admin/users that has a lot of projects. Click Edit.
  3. Change Projects limit to 1 and save.
  4. Click Impersonate in the upper right corner
  5. Navigate to /?personal=true&sort=name_asc.
  6. If you don't have any personal projects you won't see the warning. Create a personal project to see the warning.
  7. Go to /projects/new#blank_project.
  8. Choose your username from the Choose a group or namespace dropdown
  9. Fill in Project name field and click Create project. You should see an error message.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Peter Hegman

Merge request reports