Dragging tiles between columns on Issue Boards fails with "An error occurred while moving the issue. Please try again."

Summary

Attempting to drag a tile between columns on an issue board (to effectively change the related label value) fails. An error appears above the issue board that reads "An error occurred while moving the issue. Please try again." and the tile 'snaps back' to its original column. However, refreshing the page reveals that the issue tile did, in fact, get moved to the different column.

Steps to reproduce

This issue occurs on every issue board we have since updating to v16.7 of the Enterprise Edition. We make extensive use of issue boards in our company.

  • Go to an Issue Board configured with a number of columns, with each column associated with a specific label.
  • Drag a tile from one column to another.

An error appears above the issue board that reads "An error occurred while moving the issue. Please try again." and the tile 'snaps back' to its original column. However, refreshing the page reveals that the issue tile did, in fact, get moved to the different column.

Example Project

This behaviour is occurring in our self-hosted version of GitLab, so I'm unable to provide a sample project.

What is the current bug behavior?

An error appears above the issue board that reads "An error occurred while moving the issue. Please try again." and the tile 'snaps back' to its original column. However, refreshing the page reveals that the issue tile did, in fact, get moved to the different column.

What is the expected correct behavior?

The tile stays in the correct (and has the appropriate label added).

Relevant logs and/or screenshots

There are no error logs and no errors in the javascript console. Here are some screenshots illustrating the problem:

image

image

Output of checks

Results of GitLab environment info

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`)

I'm not on the team that has shell access to our GitLab server. All I've got is what's available in the 'Admin' area of the system:

> GitLab Enterprise Edition v16.7.0-ee

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