Exporting CSV with Milestone=Started results in an empty export
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Summary
Trying to export issues as CSV with a filter that includes Milestone=Started . Removing this filter (or using explicit milestone) allows it to work.
Steps to reproduce
- create an issue filter, e.g. https://gitlab.com/gitlab-org/gitlab/-/issues/?sort=created_date&state=opened&milestone_title=Started&first_page_size=20
- "Export as CSV"
- Receive email with an empty CSV file attachment
Example Project
gitlab-org/gitlab :)
What is the current bug behavior?
Empty CSV export
What is the expected correct behavior?
CSV export with a number of issues (~1600 from gitlab-org/gitlab as of writing).
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
N/A - gitlab.com
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
N/A - gitlab.com
(though was originally observed on a self-hosted 16.9 instance)
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)