Skip to main content

Adding time AM/PM

Feature Request

When I enter a time I have to keep specifying AM/PM even if the ticket was created after that.

For example, a ticket was raised at 14:50, I worked on it from 14:57 to 15:01 and the start time set itself to 2:57AM - before the ticket was raised.

It would make sense to either have a 24 hour option or for the ‘Add Time’ feature to be clever enough to know work cannot start on a ticket before the ticket is raised in most cases (maybe a toggle setting for “allow ‘Add Time’ before ticket creation”, for those who do need it).

Status: Completed9 comments

Log in to comment and vote

Comments9

  • Mikel from Gorelo

    Team

    Right now, shorthand time entries default to AM, which often feels wrong for 1 through to ~7.

    We’re proposing the following logic:

    • If no AM/PM is given, pick the version closest to now, within a window of −11h to +1h (the previous 11 hours and the next 1 hour).

    • Still allow explicit time like 4p, 115am, 1330 etc.

    🧠 If you’re logging time in arrears and that work was done in the previous 11 hours,
    this will automatically select AM/PM correctly — no extra input needed.

    We want this to work well for all MSPs, across all shifts — day, night, or 24×7.

    Does this logic feel right?

    Would a different window or behavior make more sense?

    • Harlequin Zipper

      I would posit that most people don’t enter the AM or PM when entering their times, most in my company use the numpad to enter the numbers. Input keystroke examples would be 945-tab-1000 for 945am to 10am, or 130-tab-145 for 1:30pm to 1:45pm. This is holdover muscle memory from other ticket services that has been built up over years.

      As it currently stands, 0445 and 445 both mean 4:45am while 1645 means 4:45pm. I would just shift this for business hours so that 0445 means 4:45, while 445 and 1645 mean 4:45pm. I would extend this change to all inputs from 1200 - 500. This is just a QOL fix that gives the ‘easy’ input to the day shift, which is far more staffed than the graveyard shift.

      • Mikel from Gorelo

        Team

        Hey mate,

        That sounds like the Connectwise approach

        “Times entered between 12:00 and 6:59 default to PM.”

        It’s definitely a valid approach — but one we’ve only seen in ConnectWise and not in any dedicated time-tracking tools like Toggl, Harvest, or Clockify. We’re bit hesitant to base Gorelo’s behavior purely on the ConnectWise convention, particularly when no other PSA or tracker seems to follow it.

        That said, your point about muscle memory and numpad input is fair and exactly why we’re trying to make this “just work” because there are others out there that have built up similar muscles memory from other platforms (including our own).

        If we go with the context-aware version (nearest time, within −11h / +1h),
        how often would that fail for your team’s usage?

        Are there any specific time ranges and scenarios that regularly get misinterpreted under this logic?

        Not discounting Connectwise’s approach — just want to weigh the real-world gaps on both sides so we can land on something that works across all MSPs and shifts (if that’s even possible).

        • Harlequin Zipper

          Hey Mikel,

          That system would suit almost every circumstance. The only outlier I could foresee from our normal routine operation is if a technician was doing their time entries at a different time (e.g. massive 3-full-day project, exhausted technician puts their entry in at 8am on Day 2 and it assume 800-tab-500 is 8am to 5am), but I think that these edge cases are acceptable.

          Thanks,

          Mitch

        • Amaranth Cherry

          @Mikel from Gorelo I know this feature request shipped, but I still think a preceding zero would be nice to indicate AM. It’s much quicker while staying on the numpad and goes with military time.

          Thank you and the team for the major QoL improvements surrounding time entry on the latest release! 🔥

      • Amaranth Cherry

        I too am a fan of the preceding zero indicating AM.

  • Amaranth Cherry

    Presuming business hours by default makes so much sense.

  • Harlequin Zipper

    A good way to implement this is to need a preceding 0 to indicate early AM hours. E.g. just entering 415 will default to 4:15pm, but entering 0415 will go to 4:15am. It would only be necessary to implement to prioritise 9-5, as this is when most people are entering their times.

  • Tomato Melon

    Any updates on this one? Still having to use 24hr clock