Navigate epics roadmap
Design/requirements
- Three buttons to indicate the display preference of the roadmap view.
- The default choice is the
Months
view. -
The choice is saved to the database per the user. So if the user makes a different choice, that choice is saved and will be remembered anywhere else they log in. This is per the entire instance. So this one choice carries over to all roadmap views that the user views.Moved to https://gitlab.com/gitlab-org/gitlab-ee/issues/6293
Quarters view
- Show total 6 quarters: Show the prior quarter, the current quarter, and the following 4 quarters.
- An example is below, where today is in February 2018.
- For the left-most quarter, show the year. And afterward for the rest of the quarters, only show the year if the quarter is Q1 (e.g.
2019 Q1
). - The second row shows the three months in each quarter.
Months view
- Show total of 7 months: Show the current month, the prior month, and the following 5 months.
- An example is below, where today is in the week of 2018 Jan 15–21.
- For the left-most month, show the year. And afterward for the rest of the months, only show the year if the month is January (e.g.
2019 Jan
). - The second row shows the first day of the week (here we assume that weeks start on Sundays).
Weeks view
- Show total 6 weeks: Show the prior week, the current week, and the following 4 weeks.
- An example is below, where today is May 2, 2018.
- For the left-most week, show the year. And afterward for the rest of the weeks, only show the year if the week is the first of January (e.g.
2019 Jan 6
). - The second row shows the days in each week.
Problem
While implementing #3559 (closed), we thought about listing in the roadmap all epics which have a date set (start and/or finish), even if they wouldn't have their timeline bars rendered — we didn't proceed because that work wouldn't fit in the release.
Currently, we only list and render timeline bars for epics whose dates either fall or go through the current timeframe — 3 months before and 3 months after today's date. This timeframe is fixed and cannot be changed.
Users might need to plan more into the future or see what happened in the past. We have to decide on the best approach to navigate the epics roadmap.
Key user types
When referring to “users”, we mean these specific key user types. We assume this feature will be mostly used by (in order of priority):
- Product/project managers
- Business stakeholders
Assumptions
Current assumptions that need to be proven (if possible, before implementing a solution):
-
Users plan epics 3+ months into the future -
Users see epics 3+ months in the past to plan today's and future epics -
Users don't explore the roadmap at random but have defined timeframe and granularity in mind to analyze -
Users often switch between macro and micro levels when planning and comparing
Competitors
TODO: Add links to how competitors are doing this
Goals
TODO: List desired, measurable outcomes of the user interacting with the product. Can be user-oriented, business-oriented or both.
Solutions
Some possible solutions that can be exclusive or paired (please add to this list):
- Allow users to filter the roadmap by a date range
- Allow users to control the zoom/granularity level of the roadmap
- Allow users to move the roadmap view into the past and future