I have played around with the Timeline view some and think it could use at least one important update to greatly improve the utility of it.
Currently, the timeline view always puts the text of the entity inside the element that is shown on the timeline for it. This almost never works out well for a roadmap that is going to be viewed at varying levels of date granularity, and every roadmapping tool I’ve come across provides an option to put the text outside the element.
For example, here is an excerpt of a roadmap we have in Roadmunk:
If this was in Fibery, it would say “Critical Po…” instead of “Critical Post Release Bugs” and “Opti…” instead of “Optimize Filter Bar”. If product teams are going to use Fibery for managing roadmaps, then the roadmaps need to be more readable without direct interaction. Many of our roadmaps we’ll take screenshots of and share them in meeting slides, which just wouldn’t be an effective use case at the moment.
Notion recently released a timeline view and they have a different solution of greying out the text that overflows the element, but not sure how well this works in practice.
@rothnic this is great, I am feeling that we have very similar needs from Fibery!
Could you have a look at this link:
You’ll see links to three very similar requests around word wrap limitations in Timelines, and also the whole post that link is in has some good stuff related to what you are referring to in timeline. I encourage you to “heart” away on those requests, as apparently that will increase the value of those features in the Fibery backlog, although as @Oshyan and I have discussed, the Fibery team has not come out and explained clearly how they count requests here in the forum. For example, to “hearts” on the initial post get all the value, or do responses with hearts also count?
Also, curious about your thoughts here:
And the related:
Having a secondary date on a timeline is very useful. It’s well done in Zenkit:
and your Roadmunk example is also a nice illustration of how bespoke timelines are a must in Product Development. And since Fibery is going big here, we could really use improved Timelines.
Finally, this is also a must in my book for Timelines:
Sadly, I have zero support on that one, but I remain in bad need of dependency handling in Fibery. Talk about a basic functionality in Product Development and Task Management. And something most other quality apps have with often advanced feature sets.
It will be very helpful to have a horizontal scroll bar in the timeline view.
The “Today” button centers the timeline with today in the center of the displayed timeline.
When I select the display scale as “Months” all the tasks on the timeline is from the center of the timeline view to the right with the “Today” vertical line in the center of the view.
With a horizontal scroll bar it will be possible to stay in the month scale and scroll the timeline display so that the tasks starts on the left and uses the whole timeline display to display tasks for about 30 months ahead and not only 15 months ahead from the center of the timeline view.
Hoping to amplify this feature request here! As a product manager, I would love to use Timeline views in my meetings with my stakeholders. The shortcomings noted above are inhibitors for this. I am NOT advocating for advanced Gantt chart capabilities. Rather, product managers want to be able to configure Timeline views to maximize screen real estate and readability of each object (Roadmunk’s choice to lay text on top of each horizontal line seems a reasonable solution).
Another nice to have feature would let me define the default time parameter of a Timeline view so that I can focus visibility on WIP and the upcoming 1-2 quarters.
On that note, an option to view the timeline in Quarterly increments would be a quick and important win for us.
An outcome to consider is to enable Product Managers to avoid having to build powerpoint views of timelines (roadmaps) in order to communicate info that is already in Fibery. I don’t mind taking a screenshot of Fibery for a powerpoint slide or email but I shouldn’t have to rebuild a timeline outside of Fibery. Thank you.
Milestones are nice, but when you have a lot of lanes, too many vertical lines can get confusing. Example: I have Projects as lanes on a Staffing timeline, it would be great to have the Project’s duration show on the timeline above those Staffing cards as a “summary” bar.
I have a related request (or perhaps i am just missing something). it would be great to have multiple milestones within a single timeline. Specifically, i am creating timelines for individual projects. the timeline represents the phases within the project. i would like the timeline to include multiple dates (related to the project not the phase) such as an Issue for Permit date, Construction Start date and Est Completion date
You should create a database (called Milestone perhaps) with a date field, and then link this to the Project db (one project → many milestones).
The Project’s Milestones can be added to any timeline view.
I would like to share my workaround for this problem. For “Feature” or another entity with start and end dates you can create an extra field Planned End Extended with the formula Planned.End() + Days(Length(Name) * 3). You can play and try to use another multiplier for Feature Name Length. As a result, you can use 2 timeline views:
with original start and end dates
with an original start date and new field Planned End Extended
For me and my team, a huge problem is that fields are not shown, if the timeline bar’s end is not visible.
The fields we choose to show contain important information - the fields should always be visible.
Fields should be shown right-justified if the timeline continues out of view.
The name of the entity moves along with the current field of view - it jumps to the left if you scroll, etc. Why can’t the fields do the same? This would be a great help and overall improvement for the timeline view.