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

NEW
Unassigned

Status

Firefox OS
Gaia::Calendar
P1
normal
5 years ago
3 years ago

People

(Reporter: jsmith, Unassigned)

Tracking

({user-doc-needed})

unspecified
1.1 QE4 (15jul)
ARM
Gonk (Firefox OS)
user-doc-needed

Firefox Tracking Flags

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

Details

(Whiteboard: permafail)

(Reporter)

Description

5 years ago
Followup to bug 876796. I'm still not seeing alarms getting updated on a sync.
(Reporter)

Updated

5 years ago
blocking-b2g: --- → leo?

Comment 1

5 years ago
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+

Updated

5 years ago
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
(Reporter)

Comment 3

5 years ago
(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.
(Reporter)

Updated

5 years ago
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?
(Reporter)

Comment 5

4 years ago
If we can't fix this on our end, then at a minimum we should at least user doc this.
Keywords: user-doc-needed
(Reporter)

Comment 6

4 years ago
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) → ---

Updated

4 years ago
Target Milestone: --- → 1.1 QE4 (15jul)
(Reporter)

Updated

4 years ago
Duplicate of this bug: 920107
Whiteboard: burirun1

Updated

4 years ago
Whiteboard: burirun1 → burirun1, burirun2
Whiteboard: burirun1, burirun2 → burirun1, burirun2, burirun3

Updated

4 years ago
Whiteboard: burirun1, burirun2, burirun3 → permafail
status-b2g-v1.4: --- → affected
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.0: --- → affected
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
(Reporter)

Updated

3 years ago
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
QA Whiteboard: [QAnalyst-Triage+][lead-review+] → [QAnalyst-Triage?][lead-review+]
status-b2g-v2.1: --- → affected
Flags: needinfo?(dharris)
QA Whiteboard: [QAnalyst-Triage?][lead-review+] → [QAnalyst-Triage+][lead-review+]
Flags: needinfo?(dharris)

Updated

3 years ago
QA Whiteboard: [QAnalyst-Triage+][lead-review+] → [QAnalyst-Triage?][lead-review+]
status-b2g-v2.2: --- → affected
Flags: needinfo?(dharris)
QA Whiteboard: [QAnalyst-Triage?][lead-review+] → [QAnalyst-Triage+][lead-review+]
Flags: needinfo?(dharris)
You need to log in before you can comment on or make changes to this bug.