Make roadmap column width dynamic based on date range [iteration 2]
Release notes
Problem to solve
Parker: When reporting on my team's progress, I want to view my team's planned work from from a high level down to a very granular view so that I can craft the right view for the right audience.
Currently, the way the columns interact could cause the roadmap to have large empty areas on it, especially on wide screens:
![](/-/project/278964/uploads/d687f710467644278d3fac089f8562eb/1.png)
The view on the roadmap should zoom in and out based on the selected date range and view. This will allow the user to make the best use of their screen real estate, and help them get more granular views of their data.
Intended users
User experience goal
- The roadmap is performant
- Users are able to drill into date ranges they care about
Proposal
custom range:
The user will have 4 default date ranges and the ability to create a- This month
- This quarter
- This year
- Within 3 years
- Custom
They will be able to segment their ranges in 3 different ways:
- By Quarters
- By Months
- By Weeks
Date picking
Enable the column width on the roadmap to be dynamic based on the date and view selected.
![](/-/project/278964/uploads/fd1ee5443f2b88594fb474e3746f0068/image.png)
Before | After |
---|---|
![]() |
![]() |
Before | After |
---|---|
![]() |
![]() |
Before | After |
---|---|
![]() |
![]() |
Before | After |
---|---|
![]() |
![]() |
Before | After |
---|---|
![]() |
![]() |
Before | After |
---|---|
![]() |
![]() |
Before | After |
---|---|
![]() |
![]() |
Before | After |
---|---|
![]() |
![]() |
Before | After |
---|---|
![]() |
![]() |
Before | After |
---|---|
![]() |
![]() |
Before | After |
---|---|
![]() |
![]() |
Before | After |
---|---|
![]() |
![]() |
Permissions and Security
Documentation
Availability & Testing
Available Tier
What does success look like, and how can we measure that?
- Increased usage of the roadmap
- Increased user sentiment around the roadmap
- The roadmap is more performant
Edited by Alexis Ginsberg