Roadmap: Subepics without a start or due date behavior and styling updates
Summary
From an internal slack conversation https://gitlab.slack.com/archives/C0NFPSFA8/p1586440487437100 (the whole thread is interesting)
Note how the sub-epic has no end-date, but in the roadmap view, it has an end date of 2023-12-31. If I scroll further and further to the right, the end date also updates to go further into the future. The end date for the parent epic is not updated to reflect that 2023-12-31 date nor when I scroll to the right.
Epic with no start or end date | Epic with no start or end date showing a date in roadmap |
---|---|
![]() |
![]() |
Design proposal
- Epics with no start OR end date should display this as
No start date
orNo end date
in the date value in the left column with epic titles and dates. - Epics with no start AND no end date should display this as
No start date - No end date
in the date value in the left column with epic titles and dates. - Epics that have
inherited: none
as a date are showing dates in the roadmap somehow? This should also display asNo start date
or/andNo end date
in the date value in the left column with epic titles and dates. - Epics with no start AND no end date should appear in the roadmap as:
- The epic bar should be sticky/fixed to the middle of the viewport. A user will see the starting edge and ending edge of the epic at either end of the viewport and it will never scroll off the screen horizontally.
Styling updates to epics with no start or end date indicators
- Epics with a start and end date have the current styling.
- Epics with no end date have a line break on the right of the epic bar. This line is fixed to the right edge of the roadmap view and does not scroll away. This is an indication to users that no amount of scrolling will allow them to get to the end of that roadmap item.
- Epics with no start date have a line break on the left of the epic bar. This line is fixed to the left edge of the roadmap view and does not scroll away. This is an indication to users that no amount of scrolling will allow them to get to the beginning of that roadmap item.
- Epics with no start date OR end date have a line break on the left of the epic bar AND to the right of the epic bar. These lines are fixed to the left edge and right edge of the roadmap view and do not scroll away. This is an indication to users that no amount of scrolling will allow them to get to the beginning or end of that roadmap item.
Example styling
- A. Epic with start and end date
- B. Epic with start and end date (scrolled)
- C. Epic with no start date AND no end date (line breaks are fixed even when scrolling)
- D. Epic with no start date (line break is fixed even when scrolling)
- E. Epic with no end date (line break is fixed even when scrolling)
Styling in action
View here: https://www.figma.com/proto/91s3Y0RMXy84dkvLCwg4aZ/214026-Roadmap-Subepics-without-a-start-or-due-date-behavior-and-styling-updates?node-id=1%3A10580&viewport=-29812%2C2620%2C1.3754236698150635&scaling=min-zoom
General specs for this
Steps to reproduce
&2841 (parent epic) &2917 (closed) (child epic) Were where this problem was reported, but it seems reproducible in the larger roadmap in general
Notes from @donaldcook The above may no longer apply. To reproduce:
- Create an epic with a due date
- Create a subepic without a due date.
- Go to the roadmap view. Notice the subepic shows, with an end date in the future.
This is a frontend issue, as the due date being returned in GraphQL is null
.
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?
- Epics with no start AND end date appear in the roadmap and inherit a (random?? end up view??) date.
What is the expected correct behavior?
- Epics with no start AND end date appear in the roadmap as a fixed/sticky to the middle of the roadmap viewport epic bar with the date `No start date - No end date1
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)