Fixing Settings fields unlimited pattern

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

  • Close this issue

Issue idea came from: https://gitlab.com/gitlab-org/gitlab-ce/issues/27762#note_23520780

Problem

Currently we use the character 0 for a field when something is considered unlimited. However for this to be clear, we have to specify so in the description. Also with this we aren't even consistent:

image

Proposal

We have two directions:

  1. Stating that a field is optional, thus empty is unlimited. image
  2. Having an on/off switch/checkbox to activate the field yes or no.

Which direction do we want to take?

Also we should really see if we can improve on our styling and improve our ~"UI Polish" in a big way, make it somewhat similar to this for example:

image

Although this also may have to do with considerate color choice in the application.. @pedroms 😃

Value

Be clear and consistent.

Related issues

cc: @tauriedavis @pedroms @awhildy

Edited Jun 15, 2025 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading