Ticket aging column to show days and hours (e.g. 45 days 10 hours) instead of only days

Nonprofits
,
1

Hello Monday.com Team,

I would like to request an enhancement for ticket aging calculation in monday.com.

Currently, the formula column allows us to calculate ticket aging only in days using formulas like:

DAYS(TODAY(), {Ticket Created Date})

This shows only a numeric value and does not include hours.

I would like the ticket aging column to display both days and hours in a readable format, for example:

  • 45 days 10 hours

  • 3 days 6 hours

The aging should be calculated from the ticket created date/time and ideally stop when the ticket status is marked as Resolved or Closed.

This feature would be very helpful for IT helpdesk teams, SLA tracking, and nonprofit organizations managing support tickets.

Thank you for considering this request.

2

Hey Victor!

Which tool are you using? Are you using Monday Work Management, Monday Service, or Monday CRM?

3

Hey Kevin!

Thanks for your response, I am using “Monday Work Management“.

4

Thanks, Victor!

I did a bit of testing on my end to confirm, and you’re right that the formula column can’t really do this in the way you’re looking for, but there is a different column type that can.

If I understand you correctly, you can use a “Time Tracking” column and automations that trigger when an item is created (or when a status changes) and stop when a status is set to “done”.

5

Dear Kevin,

Thank you for your response and for explaining the alternative approach.

I would like to confirm that I have already implemented the Time Tracking column with automations in my ticketing tool, as suggested. It is working as expected for tracking time between ticket creation and completion.

However, my requirement is slightly different. I am also looking for an aging column that can automatically calculate and display ticket aging in an easy-to-read format, specifically showing days along with hours (for example: 45 days 8 hours), so that the aging can be quickly understood at a glance without manual calculation.

This would be very useful from a reporting and operational perspective, especially when monitoring open tickets and SLA performance.

Please let me know if there is any existing workaround for this or if this can be considered as a feature request.

Thank you for your support.

6

Hi, Monday work management team you have any update about my concern!

7

Hey Victor,

after a little bit of back and forth with the formula column I have a working solution :slight_smile:

My setup is quite simple: I used the creation log column to take the date and time stamp from.

Screenshot 2026-02-06 at 13.37.55
Screenshot 2026-02-06 at 13.37.55656×384 34.5 KB

This is how it looks.

And this is the formula that is used:

CONCATENATE(

  ROUNDDOWN(

    (

DAYS(TODAY(), {Creation log#DateTime}) * 1440 +

      (HOUR(NOW()) * 60 + MINUTE(NOW())) -

      (HOUR({Creation log#DateTime}) * 60 + MINUTE({Creation log#DateTime}))

    ) / 1440,

  0),

  " days and ",

ROUNDDOWN(

    (

      (

DAYS(TODAY(), {Creation log#DateTime}) * 1440 +

        (HOUR(NOW()) * 60 + MINUTE(NOW())) -

        (HOUR({Creation log#DateTime}) * 60 + MINUTE({Creation log#DateTime}))

      ) -

      (ROUNDDOWN(

        (

DAYS(TODAY(), {Creation log#DateTime}) * 1440 +

          (HOUR(NOW()) * 60 + MINUTE(NOW())) -

          (HOUR({Creation log#DateTime}) * 60 + MINUTE({Creation log#DateTime}))

        ) / 1440,

      0) * 1440)

    ) / 60,

  0),

  " hours past"

)

With this setup we convert everything into a base line of minutes and then do the final calculation to show the above.

Hope that helps and works for you!

PS: You need to replace the column names with your actual column names :slight_smile:

8

Hey Dmitry,

Cool solution, I hadn’t thought of going about it this way!

A couple of things to keep in mind:

DAYS(TODAY(), created_datetime) may not be as specific as Victor needs.

TODAY() is midnight today, not “now”. So DAYS(TODAY(), created_datetime) is the time elapsed between created_datetime and 00:00 today. Then approximate “now”.

This approximation is fine most of the time, but it produces edge-case weirdness (especially around midnight or if you’re dealing with timezones).

If {Creation log#DateTime} is later today (e.g., created at 3 PM local but it’s 10 AM for another team member because of a timezone mismatch, you can get negative minutes, which can yield negative days/hours. Also your manual “minutes since midnight” math assumes a clean 24h day. DST days are 23h/25h so that would mess with those formulas on those days.

9

Dear Monday work management team,

Thank you for giving me this formula, I have some work on my workplace so, I can’t test your formula after the free time, will check and update you it’s working or not.