Expanding an epic in the roadmap doesn't refresh when the time range is expanded
Summary
Expanding epics in the roadmap sometimes results in no sub-epics being shown even when they exist. This is because a new GraphQL request isn't made when the time range is changed.
Steps to reproduce
Steps 1-3 (inclusive) are set up already in the example project.
- Create a parent epic with start date 2022-06-01, due date 2022-08-31
- Create a sub-epic (1) with start date 2022-06-27, due date 2022-07-05
- Create a sub-epic (2) with start date 2022-07-05, due date 2022-08-27
- Open the roadmap view in 'this quarter'
- Expand the epic to see only one sub-epic in range
- Open settings and set time-range to 'this year'
- Expand the now-collapsed epic
Observe that no epics are now visible. Verify that no request is made using developer tools.
Example Project
https://gitlab.com/groups/gitlab-org/plan-stage/-/epics/18
What is the current bug behavior?
Missing sub-epics are not rendered.
What is the expected correct behavior?
All sub-epics are rendered.
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)
Possible fixes
Frontend should send a new GraphQL request including the current time-range each time an epic is expanded.