Skip to content

Epics not inheriting dates

Summary

(Summarize the bug encountered concisely)

When in an epic view, I created a series of child epics and moved issues into the child epics via drag and drop.

Bug:

  • After organize my epic, subepics, and issues, I refreshed the page and clicked on the roadmap tab.
  • The roadmap tab displayed the empty state despite child epics having issues with milestones.
  • The child epics have "inherited" as the date option and it says "none" despite that epic having issues associated to a milestone with a start/end date
  • Suspect epic: &2422

Not a "bug" but annoying:

  • The counters on the parent epic did not update after adding an issue to a child epic via DnD

Steps to reproduce

(How one can reproduce the issue - this is very important)

  1. Create a parent epic with some issues in that are associated to a milestone with dates
  2. Create a child-epic from within the parent epic.
  3. Drag and drop issues from the parent epic to the child epic.
  4. Refresh the page, click on the roadmap tab. Empty state.
  5. Open the child epic and verify the date is set to Inherited. It is, but it will show "None" as the date.

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)

&2422

What is the current bug behavior?

(What actually happens)

Inherited dates aren't being reflected in child epics

What is the expected correct behavior?

(What you should see instead)

A roadmap in the parent epic and child epics having the correct inherited dates.

Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.)

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)