Forum Discussion
Problem with meeting start and end times in Microsoft Teams
Here is the workaround I found:
Type a "Exact 12-hr format" time
eg, I want to schedule a meeting at 13:33
"1333" or "13:33" doesn't work . It only accept "13:33 PM" (a space before PM)
HW_Leung That worked! The ridiculous thing is that we're on 24-hour time, but I still had to type "09:15 AM" to get it to accept 9:15 as the end time for my meeting instead of 9:30.
This is obviously a bug, but I know from experience that logging a support ticket will just get you a support engineer that tells you it's a known issue and that you can vote for it somewhere. And then nothing will be done about it. That is the low standard of quality Microsoft has sunken to, unfortunately. And as long as corporates keep blindly buying their crap, it will only get worse.
frans-wtax Well, being the optimist I submitted a support ticket anyway. I'm happy to report:
Our engineering team is aware of the situation and working towards a solution. [...] The issue reported is expected to be (fixed) by next quarter (October - December 2022).
So hopefully, the bug isn't long for this world.
- I'm glad I found this thread today! We have the same issue here
The strange thing is that I can set any time in the format "HH:MM" (as it is originally displayed) and it accepts all entries. However, several colleagues found that the time was automatically adapted to a 30-min interval (or 60 etc.). For them, the trick mentioned above to enter with the added " AM/PM" worked. The AM or PM text then vanishes because their clients are set to a 24-hour display for times.
We all have the same settings as far as I know, and our times do not show AM/PM by default. I don't know why only I have the ability to do it directly in the desktop client. We all run the same desktop version of Teams too. One colleague found that making the request online via his browser worked correctly though.- Same issue here.
In the apps the users can only use the 30-minute interval. (already deleted cache Teams)
It occurs on older versions of MS Teams and also on the newest one.
In the browser there are no issues.
