Skip to content

Issue board scrolling breaks when swim lanes are collapsed with username rendering

Summary

Issue board scrolling breaks when swim lanes displaying usernames are collapsed, due to an incorrectly sized div element overlapping the scrollbar.

Steps to reproduce

  • Navigate to an issue board with at least two swim lanes (e.g., grouped by assignee)
  • Ensure the swim lanes are displaying usernames in their titles
  • Collapse the swim lane on the right side
  • Attempt to manually scroll within the swim lane on the left side using the scrollbar

What is the current bug behavior?

When a swim lane on the right is collapsed, manual scrolling is mostly broken for the swim lane on the left. An inspection of the DOM reveals that an incorrectly sized div element (div.board-title-text) is being placed on top of the scrollbar, blocking interaction with it. This issue specifically occurs when the swim lane title is rendering a username (visible in the screenshot as the div contains user avatar elements).

What is the expected correct behavior?

The scrollbar should remain fully accessible and functional regardless of whether adjacent swim lanes are collapsed or expanded. The div.board-title-text element should not overlap or obstruct the scrollbar area, allowing users to scroll through issues in any swim lane normally.

Relevant logs and/or screenshots

Screenshot: GitLab internal only

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

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)

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.