Checkboxes in Issues updating the wrong checkbox
Summary
- In some circumstances, checking a box in an issue description updates the checkbox for a completely different checkbox.
Steps to reproduce
-
This is currently reproducable in the groupcompliance planning issue for %13.9
-
Attempt to check the box next to one of the features.
Optional enforcement of SSH key expirationdefinitely triggers this bug. -
Once checked, refresh the page. The checkbox is no longer checked, and a different one further down the page is. The event log also confirms this.
-
The GraphQL query made also matches the incorrect behaviour.
-
The lists appear to need to be in a table to cause this bug.
Example Project
What is the current bug behavior?
- Check one box
- A different one is checked in the backend and this is visible on page refresh.
What is the expected correct behavior?
- Checking a box in an issue description should check the correct box.
Output of checks
This bug happens on GitLab.com
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`)
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)