"Issues" export to CSV omits issue weight.
Summary
The export to CSV seems to get all the details I need but doesn't include the issue weight for some reason. This seems like a bug to me, especially since using issue weight is one of the reasons we paid for EE.
Running the latest omnibus version of EE.
Steps to reproduce
- Go to a project with Issues on an EE instance.
- Make sure some issues have a weight assigned.
- Click the CSV export button.
- Get the CSV in your e-mail inbox, open it.
- Notice the issue weight is not present.
What is the current bug behavior?
The CSV contains all issue fields, except issue weight.
What is the expected correct behavior?
The CSV contains all issue fields.
Relevant logs and/or screenshots
Output of checks
(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)
Results of GitLab environment info
GitLab information Version: 9.0.5-ee Revision: 71d72c9 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: postgresql DB Version: 9.6.1 URL: https://git-going.append.media HTTP Clone URL: https://git-going.append.media/some-group/some-project.git SSH Clone URL: git@git-going.append.media:some-group/some-project.git Elasticsearch: no Geo: no Using LDAP: no Using Omniauth: yes Omniauth Providers: google_oauth2
GitLab Shell Version: 5.0.0 Repository storage paths:
- default: /var/opt/gitlab/git-data/repositories Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks/ Git: /opt/gitlab/embedded/bin/git
Results of GitLab application Check
GitLab Shell version >= 5.0.0 ? ... OK (5.0.0) Repo base directory exists? default... yes Repo storage directories are symlinks? default... no Repo paths owned by git:git? default... yes Repo paths access is drwxrws---? default... yes hooks directories in repos are links: ... 4/1 ... ok 4/2 ... ok 4/3 ... ok 2/4 ... ok 2/5 ... ok 2/6 ... ok 4/8 ... ok 4/9 ... ok 4/14 ... ok 2/15 ... ok 4/17 ... ok 13/18 ... ok 4/19 ... ok 2/20 ... ok 13/21 ... ok 13/22 ... ok 4/23 ... ok Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Check GitLab API access: OK Access to /var/opt/gitlab/.ssh/authorized_keys: OK Send ping to redis server: OK gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Sidekiq ...
Running? ... yes Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Checking Reply by email ...
Reply by email is disabled in config/gitlab.yml
Checking Reply by email ... Finished
Checking LDAP ...
LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab ...
Git configured with autocrlf=input? ... yes Database config exists? ... yes All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config outdated? ... no Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory setup correctly? ... yes Init script exists? ... skipped (omnibus-gitlab has no init script) Init script up-to-date? ... skipped (omnibus-gitlab has no init script) projects have namespace: ... 4/1 ... yes 4/2 ... yes 4/3 ... yes 2/4 ... yes 2/5 ... yes 2/6 ... yes 4/8 ... yes 4/9 ... yes 4/14 ... yes 2/15 ... yes 4/17 ... yes 13/18 ... yes 4/19 ... yes 2/20 ... yes 13/21 ... yes 13/22 ... yes 4/23 ... yes Redis version >= 2.8.0? ... yes Ruby version >= 2.1.0 ? ... yes (2.3.3) Your git bin path is "/opt/gitlab/embedded/bin/git" Git version >= 2.7.3 ? ... yes (2.10.2) Active users: 1
Checking GitLab ... Finished