Can not set timezone in pipeline schedule if it was not set during first save

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

• Close this issue

Summary

Omitting setting the timezone in a pipeline schedule leads to an unrecoverable state

Steps to reproduce

• Create pipeline schedule
• Set name
• Omit timezone
• Save

--> leads to error message "Cron timezone can't be blank"

• Change time zone
• Save button keeps being disabled

What is the current bug behavior?

Setting the timezone being in this state does not allow to recover, i.e. save.

What is the expected correct behavior?

Setting the timezone should allow to save.

Relevant logs and/or screenshots

Results of GitLab environment info

Happens on Community Edition 17.11.2.

System information
System:		Ubuntu 20.04
Current User:	git
Using RVM:	no
Ruby Version:	3.2.5
Gem Version:	3.6.6
Bundler Version:2.6.5
Rake Version:	13.0.6
Redis Version:	7.2.7
Sidekiq Version:7.3.9
Go Version:	unknown

GitLab information
Version:	17.11.2
Revision:	059055d0bcc
Directory:	/opt/gitlab/embedded/service/gitlab-rails
DB Adapter:	PostgreSQL
DB Version:	16.8
URL:		https://gitlab.elnet
HTTP Clone URL:	https://gitlab.elnet/some-group/some-project.git
SSH Clone URL:	git@gitlab.elnet:some-group/some-project.git
Using LDAP:	no
Using Omniauth:	yes
Omniauth Providers: 

GitLab Shell
Version:	14.41.0
Repository storages:
- default: 	unix:/var/opt/gitlab/gitaly/gitaly.socket
GitLab Shell path:		/opt/gitlab/embedded/service/gitlab-shell

Gitaly
- default Address: 	unix:/var/opt/gitlab/gitaly/gitaly.socket
- default Version: 	17.11.2
- default Git Version: 	2.49.0.gl1