# Add Duration as a valid field type

**URL:** <https://community.fibery.io/t/add-duration-as-a-valid-field-type/3710>\
**Category:** Ideas & Features\
**Tags:** flexible-domain\
**Created:** [December 14, 2022, 4:06pm UTC](https://community.fibery.io/t/add-duration-as-a-valid-field-type/3710 "2022-12-14T16:06:26Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![julien.erny](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/julien.erny/32/5833_2.png) [@julien.erny](https://community.fibery.io/u/julien.erny)\
**Post date:** [December 14, 2022, 4:06pm UTC](https://community.fibery.io/t/add-duration-as-a-valid-field-type/3710/1 "2022-12-14T16:06:26Z")

</div>

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.)

---

<div class="post-metadata">

**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\
**Post date:** [January 1, 2025, 5:26pm UTC](https://community.fibery.io/t/add-duration-as-a-valid-field-type/3710/2 "2025-01-01T17:26:19Z")

</div>

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)

---

<div class="post-metadata">

**Author:** ![Wilco\_Boode](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/wilco_boode/32/9985_2.png) [@Wilco\_Boode](https://community.fibery.io/u/Wilco_Boode)\
**Post date:** [February 7, 2025, 7:32am UTC](https://community.fibery.io/t/add-duration-as-a-valid-field-type/3710/3 "2025-02-07T07:32:00Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![Finanzamt\_Muellheim](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/finanzamt_muellheim/32/12892_2.png) [@Finanzamt\_Muellheim](https://community.fibery.io/u/Finanzamt_Muellheim)\
**Post date:** [February 11, 2026, 4:52pm UTC](https://community.fibery.io/t/add-duration-as-a-valid-field-type/3710/4 "2026-02-11T16:52:10Z")

</div>

I am in a situation right now where I would love to have only a time field that can calculate days, hours, and minutes. I have right now a DB with an hour field and a minutes field, then a third field as a formula to calculate the total hours and minutes in decimal, but to display a sum of more hours and minutes in regular time is also a problem. I wish I could only type 2.47, and Fibery knew it was 2 hours and 47 minutes, and the SUM below understood how to SUM minutes-hours-days. 🥴

---

<div class="post-metadata">

**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\
**Post date:** [October 1, 2026, 4:25pm UTC](https://community.fibery.io/t/add-duration-as-a-valid-field-type/3710/5 "2026-10-01T16:25:12Z")

</div>

Now that we can create custom apps we can actually create more robust reports around time _but_ having a functioning duration field would help with performance. We wouldn’t need custom code to read/write decimal numbers then translate them to a time duration.
