Possibility to add activities in HHmm format (without colon)

[darioackermann]

Describe the problem

I'm a fan of using my numeric keypad to enter my hours into kimai and I'd love to be able to "speed-fill" my form by entering the start / end hour in the format HHmm (i.e., 1600 instead of 16:00).

Describe the solution you'd like

Possibility to add times in the format HHmm

Describe alternatives you've considered

No response

Screenshots

Additional info

If this has a chance of getting merged, I am happy to propose a PR for this.

[ckuetbach]

If I remember correctly, this was possible in Kimai 1.x

[darioackermann]

Thanks for linking to the other issue, I'll close this here as duplicate.

[ckuetbach]

I'm not sure, if the other issue is a direct duplicate. I linked them because I expect the fix to be at the same point in the sources and could probably be fixed together.

[kevinpapst]

Same but different => re-open

[ckuetbach]

I try to figure out, where the regular expression to check the format is created. (As I suspect a missing or wrong regex to be the cause).

This pattern: pattern="([0-9]|[01][0-9]|2[0-3]):([0-5][0-9])"

<input type="text" id="timesheet_edit_form_end_time" name="timesheet_edit_form[end_time]" pattern="([0-9]|[01][0-9]|2[0-3]):([0-5][0-9])" autocomplete="off" data-timepicker="on" data-format="HH:mm" placeholder="HH:mm" class="form-control">```

[joho1968]

I think it'd be wiser to try to do what I suggest in #4707 (comment) instead of coming up with a working regex; they're messy at best and probably won't do away with backend parsing/validation anyway ... :think

[ckuetbach]

Currently it is validated by that regex in the browser.

I'd like to remove or fix the pattern of the regular expression, because it causes my issues with the entry format. But I can't find the source code which causes the regex to be rendered into the patter attribute if the input field.

[MartinRyx]

I think it would be great to allow both 1700 and 17.00 and on lost focus parse and change to 17:00

[ebdavison]

This would definitely be great to have and be able to enter 1830 instead of 6:30 PM. Much easier on the numpad data entry muscles.

[kevinpapst]

be able to enter 1830 instead of 6:30 PM

Ah, the input is currently locale aware. So displaying and entering the time expects the same format.
That should be improved, probably its good to support both 12 and 24 hour format at the same time.