Open
Bug 1314185
Opened 8 years ago
Updated 1 month ago
[meta] Various issues around dismissing alarms need to be fixed
Categories
(Calendar :: Alarms, defect, P5)
Calendar
Alarms
Tracking
(Not tracked)
NEW
People
(Reporter: Fallen, Unassigned)
References
(Depends on 23 open bugs)
Details
(Keywords: meta)
I am opening this as a meta bug. There are various situations in which we fail to properly dismiss alarms:
* readonly calendars (bug 356002, feature request)
* Provider for Google Calendar, especially on meetings
* CalDAV, in various situations
If you are reading this bug and would like to contribute, please don't comment on this one since this is more of a tracking bug. If you can open a bug that blocks this one, we can track all the issues in a better way without mixing the different situations.
Reporter | ||
Updated•8 years ago
|
Reporter | ||
Updated•8 years ago
|
Priority: -- → P5
Comment hidden (advocacy) |
Comment hidden (obsolete) |
Comment 4•7 years ago
|
||
I've been suffering from this issue for many years now as well, having to basically delete things from my calendar to make the notifications go away. My question is: how is the priority on these bugs being determined? Does Bugzilla actually allow to track the number of affected users for each bug somehow, and would that influence the priority, like, for instance, in the Ubuntu bug tracker?
Thanks!
(In reply to Gregory Kramida from comment #4)
> I've been suffering from this issue for many years now as well, having to
> basically delete things from my calendar to make the notifications go away.
> My question is: how is the priority on these bugs being determined? Does
> Bugzilla actually allow to track the number of affected users for each bug
> somehow, and would that influence the priority, like, for instance, in the
> Ubuntu bug tracker?
>
> Thanks!
"If you are reading this bug and would like to contribute, please don't comment on this one since this is more of a tracking bug."
But, that aside, if you read this before it's deleted, I think this is fixed in TB 52.6.0 w/ Lightning 4.0.5.2 & Google Provider 3.3, because I had the problem, and now it's gone.
Comment 6•7 years ago
|
||
Never mind, sorry I overlooked this thing, I figured out how to "add" myself to the other bugs, thanks.
Updated•2 years ago
|
Severity: normal → S3
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•