Skip to content

Ctrl+enter on issue create leaves create button disabled if title is missing

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

Summary

When creating a new issue and using Ctrl+Enter to submit for saving from the body disables the "Create Issue" button when no title is present. This button is not enabled again when a title is added

Steps to reproduce

  1. On a project, press i to shortcut to a new issue page
  2. Fill in the Description area with the issue problem. Do not add a title
  3. Press Ctrl+Enter to save the issue

The validation kicks in to state that the title is a required field. The "Create issue" button becomes disabled.

Entering a title for the issue removes the validation message from the screen, but the "Create issue" button remains disabled. It does not re-enable even after changing the content

Example Project

What is the current bug behavior?

"Create Issue" button remains disabled, even when the title is present following a validation failure

What is the expected correct behavior?

When a title is added and the error message is removed from the title box, the "Create issue" button should be enabled

Relevant logs and/or screenshots

Screenshot_from_2022-05-27_09-57-47

Output of checks

Results of GitLab environment info

This happens on GitLab hosted SaaS

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of: sudo gitlab-rake gitlab:check SANITIZE=true)

(For installations from source run and paste the output of: sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)

(we will only investigate if the tests are passing)

Possible fixes

Edited by 🤖 GitLab Bot 🤖