Skip to content

Cannot Filter by Epics Created at Higher Group Levels

Summary

When trying to filter issues by epics in a project, epics from a higher level group do not show up as options to filter by.

Steps to reproduce

  1. Create a group, let's call it foo
  2. Create a subgroup within foo, let's call it bar
  3. Create a project within bar, let's call it boo

The structure should look as follows:

foo (group)
|- bar (subgroup)
   |- boo (project)
  1. Create an epic in foo called "Test Epic"
  2. Create two issues in boo called "Test Issue 1" and "Test Issue 2"
  3. Add Test Issue 1 to Test Epic
  4. Go to List or Boards view for the issues in boo
  5. Attempt to filter by Test Epic and you see the box does not show Test Epic

Example Project

What is the current bug behavior?

The filter options for epics do not populate epics created at higher group levels.

What is the expected correct behavior?

The filter options for epics do populate epics created at higher group levels.

Relevant logs and/or screenshots

opera_2020-08-05_10-30-50

Output of checks

This bug occurs on our self-hosted instance of GitLab. I am not aware if it occurs on GitLab.com or not.

Results of GitLab environment info

Expand for output related to GitLab environment info

root@gitlab:/# gitlab-rake gitlab:env:info

System information
System:
Proxy:          no
Current User:   git
Using RVM:      no
Ruby Version:   2.6.6p146
Gem Version:    2.7.10
Bundler Version:1.17.3
Rake Version:   12.3.3
Redis Version:  5.0.9
Git Version:    2.27.0
Sidekiq Version:5.2.9
Go Version:     unknown

GitLab information
Version:        13.2.1-ee
Revision:       447f057d946
Directory:      /opt/gitlab/embedded/service/gitlab-rails
DB Adapter:     PostgreSQL
DB Version:     11.7
URL:            http://gitlab:9000
HTTP Clone URL: http://gitlab:9000/some-group/some-project.git
SSH Clone URL:  ssh://git@gitlab:2200/some-group/some-project.git
Elasticsearch:  no
Geo:            no
Using LDAP:     no
Using Omniauth: yes
Omniauth Providers:

GitLab Shell
Version:        13.3.0
Repository storage paths:
- default:      /var/opt/gitlab/git-data/repositories
GitLab Shell path:              /opt/gitlab/embedded/service/gitlab-shell
Git:            /opt/gitlab/embedded/bin/git

Results of GitLab application Check

Expand for output related to the GitLab application check

root@gitlab:/# gitlab-rake gitlab:check SANITIZE=true Checking GitLab subtasks ...

Checking GitLab Shell ...

GitLab Shell: ... GitLab Shell version >= 13.3.0 ? ... OK (13.3.0) Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Internal API available: OK Redis available via internal API: OK gitlab-shell self-check successful

Checking GitLab Shell ... Finished

Checking Gitaly ...

Gitaly: ... default ... OK

Checking Gitaly ... Finished

Checking Sidekiq ...

Sidekiq: ... Running? ... yes Number of Sidekiq processes ... 1

Checking Sidekiq ... Finished

Checking Incoming Email ...

Incoming Email: ... Reply by email is disabled in config/gitlab.yml

Checking Incoming Email ... Finished

Checking LDAP ...

LDAP: ... LDAP is disabled in config/gitlab.yml

Checking LDAP ... Finished

Checking GitLab App ...

Git configured correctly? ... yes Database config exists? ... yes All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... yes Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory exists? ... yes Uploads directory has correct permissions? ... yes Uploads directory tmp has correct permissions? ... 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 3/2 ... yes 3/3 ... yes 2/4 ... yes 4/5 ... yes 3/6 ... yes 6/8 ... yes 4/9 ... yes 2/10 ... yes 4/11 ... yes 4/12 ... yes 2/13 ... yes 4/14 ... yes 14/15 ... yes 2/16 ... yes 4/17 ... yes 4/18 ... yes 50/19 ... yes 50/20 ... yes 4/21 ... yes 4/23 ... yes 4/25 ... yes 6/27 ... yes 14/28 ... yes 18/29 ... yes 4/30 ... yes 4/31 ... yes 2/34 ... yes 4/35 ... yes 4/36 ... yes 2/37 ... yes 8/38 ... yes 25/39 ... yes 36/41 ... yes 37/42 ... yes 38/43 ... yes 39/44 ... yes 40/45 ... yes 41/46 ... yes 42/47 ... yes 14/48 ... yes 43/49 ... yes 44/50 ... yes 46/51 ... yes 46/52 ... yes 45/53 ... yes 47/54 ... yes 49/55 ... yes 48/56 ... yes Redis version >= 4.0.0? ... yes Ruby version >= 2.5.3 ? ... yes (2.6.6) Git version >= 2.22.0 ? ... yes (2.27.0) Git user has default SSH configuration? ... yes Active users: ... 15 Is authorized keys file accessible? ... yes GitLab configured to store new projects in hashed storage? ... yes All projects are in hashed storage? ... no Try fixing it: Please migrate all projects to hashed storage as legacy storage is deprecated in 13.0 and support will be removed in 14.0. For more information see: doc/administration/repository_storage_types.md Elasticsearch version 6.x - 7.x? ... skipped (elasticsearch is disabled)

Checking GitLab App ... Finished

Checking GitLab subtasks ... Finished

Possible fixes

This will be fixed with the rollout of Vue-based issue lists. See #233729 (comment 754071387).

Edited by John Hope