Can add an issue TO an epic in epic view, but not in issue view

Summary

In this specific instance I can add an issue to an epic from the view of the Epic using the "Add issue" button, but I can't find the Epic when searching FROM the issue for it to add the connection there.

Steps to reproduce

  • Issue - #35583 (closed)
  • Epic - &2135
  1. Unlink them.
  2. Try to link from the Issue by searching for the Epic (not found)
  3. Go to the Epic and add the issue
  4. Link successful

Example Project

(If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report)

(If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version)

What is the current bug behavior?

(What actually happens)

What is the expected correct behavior?

(What you should see instead)

Relevant logs and/or screenshots

Screen_Shot_2019-11-14_at_12.17.21_PM

Screen_Shot_2019-11-14_at_12.17.56_PM

Output of checks

(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)

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

(If you can, link to the line of code that might be responsible for the problem)

Edited Nov 14, 2019 by Kenny Johnston
Assignee Loading
Time tracking Loading