Timeline View: Secondary dates visualization (actual vs. planned)
Now you can see secondary pair of dates on a Timeline View. The most popular use case is Planned vs. Actual dates. You can create these dates for Tasks database and fill them to see the difference:
In order to ensure consistency in field labels and behavior, weâve revamped their styles. Now, regardless of where theyâre placed, all fields have a uniform appearance.
Additionally, fields are now equipped with icons to indicate their type. Hovering over or clicking on the icon enables users to drag fields, while clicking on the field name minimizes it.
Still so much wasted space. Is there a plan to make things truly responsive on desktop at some point?
It feels like the font weight of the field names needs be be a bit heavier. Everything looks too similar and Iâd prefer field names to be semi-bold and field values to be normal.
Really awkward spacing here in the header. The padding between field titles and their values should be much smaller.
Inconsistent use of icons for field toggles. One is a toggle switch, one is an ellipses. I would also argue that at some point, toggling field visibility on the parent entity should be done in a single location instead of 2 separate locations.
Inconsistent use of font styling for â+ link/create/newâ buttons. I know these are technically different since one is used for creating/linking entities and one is used for creating fields/objects, but I would make them the same. I prefer the smaller treatment used for the â+ Link or createâ as it shouldnât be the same size as field names and values.
Somewhat relatedâŚ
I know itâs a very new feature, but the expandable headerâs UI is really rough. It ultimately wouldnât really be needed at all if you could just put any field in any order in any column. Is that where things might be going?
I wish we could decide where any field gets displayed, regardless of if itâs a relation or a document/whiteboard, or a comment, or a file, or a normal, static field. True flexibility on what field goes in what column would be bliss.
Adding a layer to that, letting entity layouts to be customized different for certain users/teams is increasing important to us, as some fields are relevant to half of our users, and other fields for the other half of users. We donât want to have to create and maintain mirrored databases just so different sets of users see clean, contextually relevant fields when looking at an entity.
Amazing updates - thank you! Could you extend the secondary dates to calendar view too? It would be great to have a calendar that shows the due dates of tasks and allow me to organise my time by drag and drop of when i plan to work on them. Here is an example i made years ago to request something similar from clickup (also includes actual worked on dates but not necessary to go that far if 2 sets of dates is maximum possible).
Secondary dates would be perfect for the example you describe. It totally applies to one of our most important things we use fibery for (resource planning for our teams).
But: as is now, it is unusable for us - As only the primary date range can be dragged and adjusted, the actual date range needs to be our primary one. We create the task directly in the timeline view. I canât see myself our my team manually updating a second date range (planned date range) for each task when creating a task⌠might seem small, but I just know that it will be forgotten half the time.
Is there any way to use a rule to fill the secondary date? I tried, but it said The last run result is not viable
What I was trying to do: when a task is created directly on the timeline, the actual date range (primary) is - of course - set. In our case, this is the planned date - until it is adjusted. So for us, it would solve the problem if an automation sets the planned date range when the task is created by using the actual date range dates from step 1. This did not work though. Any advise?
The rule should be added on Entity Creation, like this. Then when you will create an entity on a timeline it will set dates correctly. But if you change dates on timeline or anywhere, nothing will happen.
Secondary dates are awesome! Iâd love to use them, however the restriction to âone entity per laneâ mode is just too tight for my use case. Is there any chance the feature will be rolled out to the other mode as well later? (On a side note: I would actually love to set that toggle either per entity or per swimlane, and not just for the whole view)
We have zero ideas how to make it work for usual mode, since you can have many entities in a single lane and it will be very messy⌠Hiding some dates also will be weird.
My (probably naĂŻve) approach would be to to think about the âlane occupationâ as something like âword wrapâ. If an item ârequiresâ some space, others would wrap around it. That is, as I understand it, the way the âone item per lane offâ mode behaves, since sometimes things are on different ârowsâ, and sometimes they are on the same row, depending on whether their dates overlap. Couldnât it work the same for the âlargerâ secondary box? If space is needed, because the entity has a secondary date that overlaps with another entities boundaries, then a new row will open. But it would allow all other instances (where no overlap occurs) to share a row for compactness.
Edit: In keeping the analogy, for me the âone entity per laneâ button is like âinsert a newline after each wordâ, which is not the same as automatic word wrapping due to space constraints, and except for the Gannt-chart type examples you showed for timeline view, I fail to imagine how that would be useful (in timeline view or a word processor )
You may be able to achieve this using board view, if you use a database of days (and auto-link items). It would not allow drag and drop between days though.
?
Improvements
Fixed Bugs
Is there any chance the feature will be rolled out to the other mode as well later? (On a side note: I would actually love to set that toggle either per entity or per swimlane, and not just for the whole view)
)
