Issue board search button doesn't refresh data
Summary
This is a regression from v16.5.x behaviour, where it worked as expected. This has been reported by our customers, and reproduced by GitLab Support. This regression behaviour is reproducible in v16.7.x, v16.8.x, and also in GitLab.com
When modifying an issue's iteration on an issue board, when a search filter for iteration has been applied, the board data is not updated if the search button is clicked. You either need to refresh the page, or enter completely different filter criteria, so restore the board's search.
There is an issue addressing the lack of refresh in issue boards, however the issue pre-dates the recent regression of behaviour, so this issue is meant to address the specific regression. #16020
Steps to reproduce
- Ensure the project has multiple iterations from a cadence
- Open a project's issue board
- Create a new issue and assign the current iteration
- In the issue board search filter, add a filter for the current iteration
- In the issue board, change the issue's iteration to the next iteration
- Press the search button on the issue board
Example Project
https://gitlab.com/tmike_ultimate_group/zd487809/zd487809/-/boards?iteration_id=1275087
What is the current bug behavior?
Issue board results don't change after clicking the search button, the issue board results don't match the filter
What is the expected correct behavior?
Issue board results refresh after clicking the search button, the issue board results match the filter
Relevant logs and/or screenshots
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)