Closed
Bug 857284
Opened 12 years ago
Closed 10 years ago
When multiple alarms are available to fire for a calendar event, fire only one notification, not multiple notifications
Categories
(Firefox OS Graveyard :: Gaia::Calendar, defect)
Tracking
(tracking-b2g:+, b2g18?)
Tracking | Status | |
---|---|---|
b2g18 | ? | --- |
People
(Reporter: jsmith, Assigned: gaye)
References
Details
(Whiteboard: burirun1.3-2 [priority][p=8])
Attachments
(2 files)
Build: B2G 18 4/2/2013
Device: Unagi
STR
1. Import a calendar with an event that has two or more alarm reminders that would fire on import
Example - Time is 8:58pm, Event is 9pm - 10pm, reminders is 5 minutes and 15 minutes before.
Expected
We should fire only one alarm notification in this case, even though both alarms are valid here.
Actual
We fire an alarm per alarm reminder. Sort of annoying, cause your phone with sound on will make the notification noise ever single time that alarm fires. So five alarm reminders means 5 sounds in a row.
Reporter | ||
Updated•12 years ago
|
Whiteboard: [gaia-want]
Reporter | ||
Comment 1•12 years ago
|
||
Can be quite annoying when this happens. Definitely not a blocker, but we should probably get this fixed eventually.
tracking-b2g18:
--- → ?
Whiteboard: [gaia-want]
Updated•11 years ago
|
Blocks: fxos-papercuts
Updated•11 years ago
|
Whiteboard: burirun1.3-2
Updated•11 years ago
|
blocking-b2g: --- → backlog
Updated•11 years ago
|
Whiteboard: burirun1.3-2 → burirun1.3-2 [priority][p=8]
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → gaye
Assignee | ||
Updated•11 years ago
|
Target Milestone: --- → 1.3 C3/1.4 S3(31jan)
Updated•11 years ago
|
Target Milestone: 1.3 C3/1.4 S3(31jan) → 1.4 S1 (14feb)
Assignee | ||
Updated•11 years ago
|
Assignee: gaye → nobody
Target Milestone: 1.4 S1 (14feb) → ---
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → gaye
Assignee | ||
Comment 2•11 years ago
|
||
So I think these tests prove that this issue is already resolved? I have been unable to reproduce the bug.
:jsmith - Would you mind confirming whether the bug reproduces for you on master?
:millermedeiros - r?
Attachment #8390927 -
Flags: review?(mmedeiros)
Comment 3•11 years ago
|
||
Comment on attachment 8390927 [details] [review]
Link to Github pull-request: https://github.com/mozilla-b2g/gaia/pull/17171
one small nit on github but looks good to me. - nice to see the integration test coverage grow "organically".
Attachment #8390927 -
Flags: review?(mmedeiros) → review+
Assignee | ||
Comment 4•11 years ago
|
||
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Comment 5•11 years ago
|
||
Master (1.5), Nexus 4, built 3/24
Multiple notifications from a single event on a Zimbra-synced calendar.
I got 4 notifications for a meeting at 5pm. They were all within a fairly short period before the meeting.
I cleared those notifications, and then got two more 35 minutes after 5pm.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Assignee | ||
Comment 6•10 years ago
|
||
Also reported by Lucas and work happening for 2.0 in 1018834
Status: REOPENED → RESOLVED
Closed: 11 years ago → 10 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Comment 7•10 years ago
|
||
Not duplicate. Lucas' bug is that the reminders get persisted to the server. Yikes!
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Comment 9•10 years ago
|
||
maybe :dietrich bug is something different? see Bug 865394
Assignee | ||
Comment 10•10 years ago
|
||
Before we were streaming our alarms straight to the notifications controller if they were meant to trigger in the past. This patch pulls all of the alarms we're going to issue into memory first, groups the ones we're sending straight to the notifications controller by event and then only issues a single notification. Still need to add tests :)
Attachment #8514592 -
Flags: review?(mmedeiros)
Comment 11•10 years ago
|
||
Comment on attachment 8514592 [details] [review]
Link to Github pull-request: https://github.com/mozilla-b2g/gaia/pull/25673
LGTM
Attachment #8514592 -
Flags: review?(mmedeiros) → review+
Assignee | ||
Comment 12•10 years ago
|
||
fixed, landed on master https://github.com/mozilla-b2g/gaia/commit/80fd4b51714ec936ae3230e76b5b773b5a79c64c
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•10 years ago
|
Target Milestone: --- → 2.1 S8 (7Nov)
Comment 13•10 years ago
|
||
[Environment]
Gaia-Rev 4c159e75a1568afbbf0c83c1235ec56facfbe87d
Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/b9849b3c6aaa
Build-ID 20141111161207
Version 34.0
Device-Name flame
FW-Release 4.4.2
FW-Incremental 39
FW-Date Thu Oct 16 18:19:14 CST 2014
Bootloader L1TC00011880
[Result]
PASS
Status: RESOLVED → VERIFIED
Updated•10 years ago
|
blocking-b2g: backlog → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•