"dashboard/issues" page always returns 502 HTTP error

Summary

https://gitlab.com/dashboard/issues always returns 502 "Whoops, GitLab is taking too much time to respond."

Steps to reproduce

1. Sign in to GitLab
2. Go to https://gitlab.com/dashboard/issues

What is the current bug behavior?

502 "Whoops, GitLab is taking too much time to respond." page is shown.

What is the expected correct behavior?

Dashboard issues page should be shown.

Relevant logs and/or screenshots

Output of checks

This bug happens on GitLab.com

@EvgenyOrekhov It's probably best not to do that on GitLab.com. You'll be listing all issues that are available to you across the whole of GitLab.com. The length of the query will cause the request to time out. When looking at issues you should use the project/issues, group/issues to scope to project or group or Dashboard issues link in the nav bar to scope the issues assigned to your user account.

added ~14281 ~18308 labels

@markglenfletcher Well it's GitLab.com that suggests me to go to "dashboard/issues".

@EvgenyOrekhov Indeed, you're right and that isn't scoped

mentioned in issue #30837 (closed)

/cc @adamniedzielski

added ~874211 label

mentioned in issue #31204 (moved)

Thanks for reporting this @EvgenyOrekhov! It's a duplicate of https://gitlab.com/gitlab-org/gitlab-ce/issues/27496 and https://gitlab.com/gitlab-org/gitlab-ce/issues/25504, but I found your https://gitlab.com/gitlab-org/gitlab-ce/issues/30265#note_26505153 valuable so I opened https://gitlab.com/gitlab-org/gitlab-ce/issues/31204.

closed