May 20 2021 08:58 AM
May 20 2021 08:58 AM
I found that you have to edit the meeting title and time on the registration page to match the actual meeting time of the event. Is anyone else seeing this? Is this by design?
Jun 01 2021 09:06 AM
Hi @David Phillips, this is a known issue and will be corrected in our next update to the webinar feature (Q3CY21).
Jun 01 2021 09:57 AM
@Bryan Nyce @David Phillips I have noticed that if you set all the event details before turning on the requirement for registration that the registration page will pick-up the correct date and time. However, it would be nice if the date and time on the registration form was automatically updated with changes to dates and times of the event. In addition, it is frustrating that if you don't set the event details before turning registration for the webinar on then the start/end times on your registration page are limited to the hour/half-hour meaning your registration page might not match-up to your event details. This is confusing for participants.
Oct 07 2021 09:27 AM
@Tmadel It looks like this is not yet fixed because it just happened to one of our users :(
Oct 15 2021 09:10 AM
@RolandGoguen and others,
Apologies, but spoke with the feature PM, and this work has been pushed back into H1CY22 timeframe (potentially end Q1CY22/early Q2CY22 at the moment).
Oct 21 2021 03:30 PM
@Bryan Nyce - truly disappointing. I hope that the PM understands the adverse impact that this bug has on the product. Because it can completely confuse the attendee - we are not using the Webinar product, even though we would very much like to do so. This is a major bug in the system and should be corrected ASAP.
Nov 03 2021 05:25 PM
Dec 06 2021 02:10 AM
Dec 10 2021 03:22 PM
@ARusteika_LTG This is really upsetting. Microsoft created a significant bug in a feature that makes it unusable by most of their paying customers... it is taking them ~one year to address this issue. Whoever is the product owner for this capability should really talk to their customers to understand that they rolled out a product which many want to use, but it is UNUSABLE due to this bug. How come this was not a priortity fix in their next possible release?