User Community Feedback

Submitted ideas will be evaluated by our product teams for upcoming releases and will be responded to so you know where things stand. For product support, please use the community forums or contact TAC.

NOTE: All Cisco employees & Channel Partners must enter Ideas through this Ideas Portal.

More detail returned in reports API

Please include original time zone of the scheduled meeting. As well, in the recurrence field, indicate how many recurring events there are. Is it a 3 day recurrence or a 5 day recurrence? Currently it states whether the recurrence is daily or weekly, and the date (only the date) when the recurrence stops. The problem is, if a "meeting day" spans across two days (in UTC), when does the recurrence end? A 9 to 5 meeting in Mountain time zone ends at midnight UTC, which is really the next day (in UTC). But the expiry date is really in local time. If the recurrence expires on Jan 27, 2022, and the meeting is supposed to be over at 5:00 pm Mountain on the 27th, that's actually Jan 28, 2022 0:00 UTC, yet the report shows it expiring at Jan 27, 2022 0:00, because in local time when the meeting expires, it's still Jan 27. So that's a bug.

  • Guest
  • Jan 20 2022
  • Junyi Chu commented
    15 Feb, 2022 02:51am

    Ehric - forward you to take a look.