Maintenance Mode: Form UX Bugs
Summary
When updating Maintenance Mode there are some backend restrictions that are not reflected in UI that can cause minor work/time loss.
Backend Restrictions:
- Banner message cannot exceed 255 characters
- Banner messages are not saved if the user doesn't also enable maintenance mode
- Banner messages previously saved are erased if user disables maintenance mode
Steps to reproduce
Attempt to save the form after doing breaking one of the above 3 listed restrictions.
What is the current bug behavior?
Results:
- Fails with generic error message
There was an error updating the Maintenance Mode Settingsand banner message is erased after user attempts to save. - Banner message is simply erased after user attempts to save.
- Banner message is erased after user attempts to save.
What is the expected correct behavior?
It is expected that the form would properly inform and possibly restrict the user from performing a save action that could result in their configurations being lost.
Relevant logs and/or screenshots
| Restriction 1 | Restriction 2 | Restriction 3 |
|---|---|---|
| Restriction 1 | Restriction 2 | Restriction 3 |
Possible fixes
Implementing a solution that properly validates the form on the UI before attempting to save as well as informing users of when actions they take will result in configuration changes.
Screen_Recording_2025-07-29_at_12.17.37_PM
Patch release information for backports
If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.
Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.
High-severity bug remediation
To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.