Closed Bug 887871 Opened 12 years ago Closed 7 years ago

Followup to bug 876796 - Editing a Google Calendar event on the server to a different time amount for an alarm does not change the client on sync

Categories

(Firefox OS Graveyard :: Gaia::Calendar, defect, P1)

ARM
Gonk (Firefox OS)
defect

Tracking

(blocking-b2g:-, b2g-v1.4 affected, b2g-v2.0 affected, b2g-v2.1 affected, b2g-v2.2 affected)

RESOLVED WONTFIX
1.1 QE4 (15jul)
blocking-b2g -
Tracking Status
b2g-v1.4 --- affected
b2g-v2.0 --- affected
b2g-v2.1 --- affected
b2g-v2.2 --- affected

People

(Reporter: jsmith, Unassigned)

References

Details

(Keywords: user-doc-needed, Whiteboard: permafail)

Followup to bug 876796. I'm still not seeing alarms getting updated on a sync.
blocking-b2g: --- → leo?
missing alarm notifications because its not syncing is breaking core functionality. we can't have people miss their alarms that they set against the phone.
blocking-b2g: leo? → leo+
Priority: -- → P1
Target Milestone: --- → 1.1 QE4 (15jul)
Can we verify that this works when another field in the event has changed? Google has a bug where if the user changes only the alarm we don't get a notification of the update. If the title and or description/time is updated then it should work.
Keywords: qawanted
(In reply to James Lal [:lightsofapollo] from comment #2) > Can we verify that this works when another field in the event has changed? > Google has a bug where if the user changes only the alarm we don't get a > notification of the update. If the title and or description/time is updated > then it should work. This works fine with time changes, notes changes, and title changes. It appears to be alarms-specific.
Keywords: qawanted
OK- then this is a Google bug- I don't know what we can do on our end... Moving to leo? I raised the issue with my google contact but I don't have any way to track it.
blocking-b2g: leo+ → leo?
If we can't fix this on our end, then at a minimum we should at least user doc this.
Keywords: user-doc-needed
Adding some SUMO team members to the cc list to see if they can help with documenting this known issue for 1.1.
Removing tracking here since we cannot fix this in our side and lets follow-up offline on the outreach to google here. James, can you please let us know if the outreach you've made is progressing, else I will follow-up with Lawrence who may have contacts.
blocking-b2g: leo? → -
(clearing QE4 target because it's not leo+)
Target Milestone: 1.1 QE4 (15jul) → ---
Target Milestone: --- → 1.1 QE4 (15jul)
Whiteboard: burirun1
Whiteboard: burirun1 → burirun1, burirun2
Whiteboard: burirun1, burirun2 → burirun1, burirun2, burirun3
Whiteboard: burirun1, burirun2, burirun3 → permafail
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
QA Whiteboard: [QAnalyst-Triage+][lead-review+] → [QAnalyst-Triage?][lead-review+]
Flags: needinfo?(dharris)
QA Whiteboard: [QAnalyst-Triage?][lead-review+] → [QAnalyst-Triage+][lead-review+]
Flags: needinfo?(dharris)
QA Whiteboard: [QAnalyst-Triage+][lead-review+] → [QAnalyst-Triage?][lead-review+]
Flags: needinfo?(dharris)
QA Whiteboard: [QAnalyst-Triage?][lead-review+] → [QAnalyst-Triage+][lead-review+]
Flags: needinfo?(dharris)
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.