tree 7f298103d8127b52aac541fa2fb2ff6bbd29c5f8
parent 89061dd2ba79bc8869a907b92c1af909d3b0aff3
author Marc Blank <mblank@google.com> 1278107591 -0700
committer Marc Blank <mblank@google.com> 1278107591 -0700

Interpret "busy" on new events to mean "no response"

* The meaning of a busy status of "Busy" is uncertain; it could mean
  "Accepted" or "Tentative", depending on whether the event was
  created via OWA/Outlook or EAS
* We have interpreted it as "Accepted", which prevents the user from
  actually accepting the event (as a state change is required for us
  to send updates to the server/organizer)
* This CL changes the behavior such that a newly arriving event with
  a "Busy" status is shown as "No response" in the Calendar, thereby
  allowing the user to pick from any of the three possible options.

Bug: 2811859
Change-Id: Ie2c375278b79b47dedac02472dfe6e4cf1182b65