Roadmap child epic due date not matching up with dates on top
Summary
Child epics within the roadmap due dates aren't matching up with the dates presented on the top portion of the road map. This issue is noticeable if you create a child epic that has a 1 day due date (For example May 1 - May 2) and a 3 day due date (May 8 - May 11)
I have included a screenshot with white lines that I edited to illustrate the issue described above.
Steps to reproduce
- Go to Epics on the left side of GitLab.
- Create a parent epic.
- Within the parent epic create the first child epic. Assign any start date, for the due date, ensure that it's due 1 day from the start date. For example May 1 - May 2.
- Within the parent epic create the second child epic. Assign any start date, for the due date, pick a due date that's due 3 days from the start date. For example May 8 - May 11.
- Go to Roadmap, you will see that the due date does not match up with the date presented on the top portion of the roadmap.
What is the current bug behavior?
When creating a child epic, the due date isn't matching up with the visual dates presented on the top of the roadmap.
What is the expected correct behavior?
The child epic due date should match up with the dates presented on the top of the roadmap.
Output of checks
This bug happens on GitLab.com, as well as GitLab 16.8.1.
Results of GitLab environment info
Customer reported this on a self-managed instance of GitLab 16.8.1, however I have reproduced it on GitLab.com.
Edited by Rommel R