Currently the timeline view allows the timeframe visible to be at the day level, and includes hourly granularity at this level. It would be helpful to have hourly granularity on the timeline view, also when viewing a week, 2 week or month timeframe. For example, we built a guest management and reservation system for our client. But in order to display the reservations in a single line by cabin on the week, 2 week or month timeframe on the timeline view we have to have the end date be one short day of the actual departure. The alternative is to use the actual departure date, which is also the arrival date of the incoming reservation. If we use the actual departure date, the reservations are forced onto two lines because they overlap at the day level. If we could have hourly granularity at the week, two week and monthly level, they would not overlap because checkout time is at 11am on the day of departure and time of arrival is 4pm on day of arrival. ..
How does is solve the user problems?
Since we have to use the the day prior to the actual departure date to get the reservations to line up in a single line, the date displayed on the timeline view when the user hovers is incorrect since it's displaying the Departure-1 Date.
It makes the timeline view more accurate and more easily understood...
How was this validated?
Who is the target audience?
Anyone that uses the timeline view and prefers a weekly to monthly timeframe.