Skip to content

Sub-Epic Not Visible in Ancestor Epic, but shows it's added in activity

Summary

When I add a sub-epic to an ancestor epic, I can initially see the visual drop down menu (relationship) between the two and any issues that may also be correlate with that sub-epic. If I refresh or leave and come back to that page, it no longer shows the Epic-Child Epic hierarchy, but does still show it was added in activity. The sub-epic shows the parent as ancestor in its sidebar.

Steps to reproduce

Add a sub-epic to an epic (maybe have some issues in the sub-epic)

Example Project

Ancestor epic:

tech-marketing/demos/gitlab-agile-demo/multinational-technology-company&3

Child epic:

tech-marketing/demos/gitlab-agile-demo/multinational-technology-company/billing&3

What is the current bug behavior?

The visual relationship disappears

What is the expected correct behavior?

The visual relationship is shown as expected

Relevant logs and/or screenshots

Created an epic in a separate sub-group Screen_Shot_2020-01-06_at_4.54.08_PM

Then added it to an epic at the ancestor group Screen_Shot_2020-01-06_at_4.54.45_PM

Refreshed page and visual disappears but still shows in activity Screen_Shot_2020-01-06_at_4.55.05_PM

Visiting the sub-epic shows the parent as ancestor in the sidebar Screen_Shot_2020-01-06_at_6.19.17_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 by John Hope