Today, Duration is not a valid field type so you necessarily have to convert a duration in days, hours or minutes. It would be great to have the Duration be a full class citizen in fields with a textual representation dynamically adapting to the length of time (34s → 1m23s → 2h34m → 2d → 3w → etc.)
1 Like
I’m working on a system to improve reporting on time spent on projects.
Today, Fibery can only perceive time if it uses a datetime field. We either use datetime fields or convert time to decimals.
In my Time Log database each record is a summary of all time spent on the project per person. A duration field type would make it possible to sum up the number of hours and minutes spent on a project and show them as a time value.
I think it would be important for the data type should to let us choose between 24h output and a string (25:30:00 vs 1d 1h 30m vs 25h 30m)
1 Like
I’d like to bump this request up.
We have quite some databases where a generic duration field is handy, like when we store information about playtest sessions and we dont care (or know) about the exact start/end, but only want to store the time it took.
Any info on the implementation of a generic time field that can represent time / duration?